APPS account was locked and expired
bash-2.05b$ FNDCPASS apps/xxxxx 0 Y system/manager SYSTEM APPLSYS xxxx
APP-FND-01564: ORACLE error 28000 in AFPCOA
Cause: AFPCOA failed due to ORA-28000: the account is locked
.
The SQL statement being executed at the time of the error was: and was executed from the file .
So just unlock the password
SQL> alter user apps account unlock;
User altered.
SQL> conn apps/xxxxx
Connected.
Note 364614.1:Best Practices for Securing the E-Business Suite
Note 114930.1:Oracle Password Management Policy
Note 420001.1:adpatch Ora-28000 Account Locked apps
Saturday, May 22, 2010
Sunday, May 9, 2010
Oracle's Optimal Flexible Architecture
Oracle's Optimal Flexible Architecture (OFA) is a great way to apply standards and best practices for a large Oracle shop, especially those who must manage multiple databases in many environments.
See this link for a full copy of Oracle's Optimal Flexible Architecture (OFA) standard.
The 11g New Features Guide notes important OFA changes, namely the removal of $ORACLE_HOME as an anchor for diagnostic and alert files:
"The database installation process has been redesigned to be based on the ORACLE_BASE environment variable. Until now, setting this variable has been optional and the only required variable has been ORACLE_HOME.
With this feature, ORACLE_BASE is the only required input, and the ORACLE_HOME setting will be derived from ORACLE_BASE."
Let's take a look at changes to the Oracle11g OFA standard.
Enter new admin subdirectories
New in Oracle 11g we see the new ADR (Automatic Diagnostic Repository) and Incident Packaging System, all designed to allow quick access to alert and diagnostic information.
The new $ADR_HOME directory is located by default at $ORACLE_BASE/diag, with the directories for each instance at $ORACLE_HOME/diag/$ORACLE_SID, at the same level as the traditional bdump, udump and cdump directories and the initialization parameters background_dump_dest and user_dump_dest are deprecated in 11g.
You can use the new initialization parameter diagnostic_dest to specify an alternative location for the diag directory contents.
In 11g, each $ORACLE_HOME/diag/$ORACLE_SID directory may contain these new directories:
alert - A new alert directory for the plain text and XML versions of the alert log.
incident - A new directory for the incident packaging software.
incpkg - A directory for packaging an incident into a bundle.
trace - A replacement for the ancient background dump (bdump) and user dump (udump) destinations.
cdump - The old core dump directory retains it's 10g name.
Let's see how the 11g alert log has changed.
Alert log changes in 11g
Oracle now writes two alert logs, the traditional alert log in plain text plus a new XML formatted alert.log which is named as log.xml.
Prior to Oracle 11g, the alert log resided in $ORACLE_HOME/admin/$ORACLE_SID/bdump directory, but it now resides in the $ORACLE_BASE/diag/$ORACLE_SID directory.
Fortunately, you can re-set it to the 10g and previous location by specifying the BDUMP location for the diagnostic_dest parameter.
But best of all, you no longer require server access to see your alert log since it is now accessible via standard SQL using the new v$diag_info view:
select name, value from v$diag_info.
See this link for a full copy of Oracle's Optimal Flexible Architecture (OFA) standard.
The 11g New Features Guide notes important OFA changes, namely the removal of $ORACLE_HOME as an anchor for diagnostic and alert files:
"The database installation process has been redesigned to be based on the ORACLE_BASE environment variable. Until now, setting this variable has been optional and the only required variable has been ORACLE_HOME.
With this feature, ORACLE_BASE is the only required input, and the ORACLE_HOME setting will be derived from ORACLE_BASE."
Let's take a look at changes to the Oracle11g OFA standard.
Enter new admin subdirectories
New in Oracle 11g we see the new ADR (Automatic Diagnostic Repository) and Incident Packaging System, all designed to allow quick access to alert and diagnostic information.
The new $ADR_HOME directory is located by default at $ORACLE_BASE/diag, with the directories for each instance at $ORACLE_HOME/diag/$ORACLE_SID, at the same level as the traditional bdump, udump and cdump directories and the initialization parameters background_dump_dest and user_dump_dest are deprecated in 11g.
You can use the new initialization parameter diagnostic_dest to specify an alternative location for the diag directory contents.
In 11g, each $ORACLE_HOME/diag/$ORACLE_SID directory may contain these new directories:
alert - A new alert directory for the plain text and XML versions of the alert log.
incident - A new directory for the incident packaging software.
incpkg - A directory for packaging an incident into a bundle.
trace - A replacement for the ancient background dump (bdump) and user dump (udump) destinations.
cdump - The old core dump directory retains it's 10g name.
Let's see how the 11g alert log has changed.
Alert log changes in 11g
Oracle now writes two alert logs, the traditional alert log in plain text plus a new XML formatted alert.log which is named as log.xml.
Prior to Oracle 11g, the alert log resided in $ORACLE_HOME/admin/$ORACLE_SID/bdump directory, but it now resides in the $ORACLE_BASE/diag/$ORACLE_SID directory.
Fortunately, you can re-set it to the 10g and previous location by specifying the BDUMP location for the diagnostic_dest parameter.
But best of all, you no longer require server access to see your alert log since it is now accessible via standard SQL using the new v$diag_info view:
select name, value from v$diag_info.
Friday, May 7, 2010
Mounting a Windows XP NTFS partition in Linux
Mounting a Windows XP NTFS partition in Linux
How to access a Windows XP or Vista NTFS partition from Linux. The following tutorial explains how to gain access to a Windows NTFS partition using Linux. Reading or accessing NTFS partitions in Linux is important for many reasons. Some users repair Windows Operating environments using Linux, while others use a dual boot operating environment and would like to have access to their Windows File system.
The good news is that this is not a complicated task to accomplish. As a matter of fact, for those using a Linux version derived from Debian, (I.E. Ubuntu, Knoppix, etc…) the process can be accomplished in a matter of seconds.
How to Mount a Windows NTFS file system partition in Linux:
NOTE: In step four of the following tutorial, replace hdx1 with your actual partition found in step two. For example hda1, hdb2, sda1, etc.
Open a terminal and type sudo su
Type fdisk -l (note which partition contains the NTFS file system)
Type mkdir /media/windows (This directory is where we will access the partition)
Type mount /dev/hdx1 /media/windows/ -t ntfs -o nls=utf8,umask=0222
Type cd /media/windows (Moves us to the windows directory)
Type ls to list the files on the NTFS partition
Notes: Alternately, you can navigate to the media/windows directory outside of terminal to view the files.
To unmount the Windows NTFS partiton, from the terminal simply type umount /media/windows/
How to access a Windows XP or Vista NTFS partition from Linux. The following tutorial explains how to gain access to a Windows NTFS partition using Linux. Reading or accessing NTFS partitions in Linux is important for many reasons. Some users repair Windows Operating environments using Linux, while others use a dual boot operating environment and would like to have access to their Windows File system.
The good news is that this is not a complicated task to accomplish. As a matter of fact, for those using a Linux version derived from Debian, (I.E. Ubuntu, Knoppix, etc…) the process can be accomplished in a matter of seconds.
How to Mount a Windows NTFS file system partition in Linux:
NOTE: In step four of the following tutorial, replace hdx1 with your actual partition found in step two. For example hda1, hdb2, sda1, etc.
Open a terminal and type sudo su
Type fdisk -l (note which partition contains the NTFS file system)
Type mkdir /media/windows (This directory is where we will access the partition)
Type mount /dev/hdx1 /media/windows/ -t ntfs -o nls=utf8,umask=0222
Type cd /media/windows (Moves us to the windows directory)
Type ls to list the files on the NTFS partition
Notes: Alternately, you can navigate to the media/windows directory outside of terminal to view the files.
To unmount the Windows NTFS partiton, from the terminal simply type umount /media/windows/
Prerequisites and Drive Types:
Prerequisites and Drive Types:
Prerequisite: This tutorial covers adding a new disk drive to your linux computer. First it is assumed that the hard drive was physically added to your system.
IDE based systems, can support two drives on each ribbon cable. The cable is attached to either the Primary or Secondary IDE controller. A "jumper" is pressed onto two pins (thus connecting the two pins) on the drive to define the drive as a "Master" or a "Slave" drive. Each cable can support one master and one slave drive. Typically new desktop systems have one hard drive connected as a Master on the Primary controller and one CD-Rom on the second cable configured as a master.
SCSI drives will have jumpers positioned to assign a SCSI device ID number typically numbered 1-8. A sticker on the top of the drive will often show a diagram of jumper placement for drive assignment.
--------------------------------------------------------------------------------
Linux Hard Drive Naming Convention:
IDE drives are referred to as hda for the first drive, hdb for the second etc...IDE uses separate ribbon cables for primary and secondary drives. The partitions on each drive are referred numerically. The first partition on the first drive is referred to as hda1, the second as hda2, the third as hda3 etc ...
Linux IDE naming conventions:
Device Description Configuration
/dev/hda 1st (Primary) IDE controller Master
/dev/hdb 1st (Primary) IDE controller Slave
/dev/hdc 2nd (Secondary) IDE controller Master
/dev/hdd 2nd (Secondary) IDE controller Slave
Note: SCSI disks are labeled /dev/sda, /dev/sdb, /dev/sdc etc... to represent the first, second, third,... SCSI hard drive devices but not the SCSI ID. SCSI hard drive partitions are represented by an additional number. i.e. First drive first partition, /dev/sda1, second partition, /dev/sda2,... Other SCSI devices such as tape backup are labeled /dev/st0 for the first, /dev/st1 for the second and so forth. See YoLinux SCSI tutorial for more info.
--------------------------------------------------------------------------------
Command and Response Dialog of Adding a New IDE Drive:
As root perform the following: (as highlighted in bold)
[root]# fdisk /dev/hdb
Command (m for help): m (Enter the letter "m" to get list of commands)
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
Command (m for help): n
Command action
e extended
p primary partition (1-4)
e
Partition number (1-4): 1
First cylinder (1-2654, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-2654, default 2654):
Using default value 2654
Command (m for help): p
Disk /dev/hdb: 240 heads, 63 sectors, 2654 cylinders
Units = cylinders of 15120 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 1 2654 20064208+ 5 Extended
Command (m for help): w (Write and save partition table)
[root]# mkfs -t ext3 /dev/hdb1
mke2fs 1.27 (8-Mar-2002)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
2508352 inodes, 5016052 blocks
250802 blocks (5.00%) reserved for the super user
First data block=0
154 block groups
32768 blocks per group, 32768 fragments per group
16288 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 34 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[root]# mkdir /opt2
[root]# mount -t ext3 /dev/hdb1 /opt2
Note: A computer system may have multiple drives with primary partitions but only one primary partition may be active on one drive only. The active primary partition is used for booting the system and is referenced by the Master Boot Record (MBR). Each hard drive may only have a maximum of four primary partitions. One may only boot an OS from a primary partition. Extended partitions allow one to place up to 24 partitions on a single drive.
The above example shows the addition of a drive as one whole extended partition used to extend the storage space of the system. It was not created to hold additional operating systems as this would require a primary partition. Primary partitions can be used to extend the storage space of the system as well. It is not precluded from such a function but it will then limit you to four partitions for that hard drive.
--------------------------------------------------------------------------------
File: /etc/fstab
Enter the drive into the fstab file so that it is recognized and mounted upon system boot.
File: /etc/fstab Red Hat 8.0
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hda2 swap swap defaults 0 0
/dev/hdb1 /opt2 ext3 defaults 1 2
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0
The digits "1 2" refer to whether the mount point should be backed up when the dump command is used and disk integrity checks using fsck. The "1" states that it should be backed up when the dump command is issued (0=no). The "2" refers to the order in which "fsck" should check the mount points. The digit "1" identifies the root ("/") of the filesystem. All others should be "2". (0=no check)
Also see: fstab man page for a description of all options.
--------------------------------------------------------------------------------
Links
YoLinux Tutorial: System Administration - [Filesystems and drives]
YoLinux Tutorial: System optimization - Hard drive performance optimizations
Hard Drive Partitions - Definitions
Partitions - Tools, best practices, explanations
Man pages:
e2label - Add label to hard drive: e2label /dev/hdb EXTRA_DRIVE
Note: Labels support up to 16 characters.
fdisk - Manipulate/configure the partition table.
sfdisk - Manipulate/configure the partition table.
cfdisk - Curses based disk partition table manipulator.
mkfs - Build Linux file system. (Actually a front-end to various file system builders for various file system types.)
mke2fs - Create a Linux second extended file system.
tune2fs - Adjust file system parameters on a second extended filesystem. Convert ext2 to ext3, add volume label (-L), ...
mount - Mount a file system
fstab - Configuration file for mounting filesystems.
SCSI Drives:
Scsihosts - Kernel boot time module introduced in the stable release kernel 2.4. Controls SCSI device ordering.
Linux 2.4 SCSI subsystem HOWTO - [tldp]
YoLinux SCSI Info
Prerequisite: This tutorial covers adding a new disk drive to your linux computer. First it is assumed that the hard drive was physically added to your system.
IDE based systems, can support two drives on each ribbon cable. The cable is attached to either the Primary or Secondary IDE controller. A "jumper" is pressed onto two pins (thus connecting the two pins) on the drive to define the drive as a "Master" or a "Slave" drive. Each cable can support one master and one slave drive. Typically new desktop systems have one hard drive connected as a Master on the Primary controller and one CD-Rom on the second cable configured as a master.
SCSI drives will have jumpers positioned to assign a SCSI device ID number typically numbered 1-8. A sticker on the top of the drive will often show a diagram of jumper placement for drive assignment.
--------------------------------------------------------------------------------
Linux Hard Drive Naming Convention:
IDE drives are referred to as hda for the first drive, hdb for the second etc...IDE uses separate ribbon cables for primary and secondary drives. The partitions on each drive are referred numerically. The first partition on the first drive is referred to as hda1, the second as hda2, the third as hda3 etc ...
Linux IDE naming conventions:
Device Description Configuration
/dev/hda 1st (Primary) IDE controller Master
/dev/hdb 1st (Primary) IDE controller Slave
/dev/hdc 2nd (Secondary) IDE controller Master
/dev/hdd 2nd (Secondary) IDE controller Slave
Note: SCSI disks are labeled /dev/sda, /dev/sdb, /dev/sdc etc... to represent the first, second, third,... SCSI hard drive devices but not the SCSI ID. SCSI hard drive partitions are represented by an additional number. i.e. First drive first partition, /dev/sda1, second partition, /dev/sda2,... Other SCSI devices such as tape backup are labeled /dev/st0 for the first, /dev/st1 for the second and so forth. See YoLinux SCSI tutorial for more info.
--------------------------------------------------------------------------------
Command and Response Dialog of Adding a New IDE Drive:
As root perform the following: (as highlighted in bold)
[root]# fdisk /dev/hdb
Command (m for help): m (Enter the letter "m" to get list of commands)
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
Command (m for help): n
Command action
e extended
p primary partition (1-4)
e
Partition number (1-4): 1
First cylinder (1-2654, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-2654, default 2654):
Using default value 2654
Command (m for help): p
Disk /dev/hdb: 240 heads, 63 sectors, 2654 cylinders
Units = cylinders of 15120 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 1 2654 20064208+ 5 Extended
Command (m for help): w (Write and save partition table)
[root]# mkfs -t ext3 /dev/hdb1
mke2fs 1.27 (8-Mar-2002)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
2508352 inodes, 5016052 blocks
250802 blocks (5.00%) reserved for the super user
First data block=0
154 block groups
32768 blocks per group, 32768 fragments per group
16288 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 34 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[root]# mkdir /opt2
[root]# mount -t ext3 /dev/hdb1 /opt2
Note: A computer system may have multiple drives with primary partitions but only one primary partition may be active on one drive only. The active primary partition is used for booting the system and is referenced by the Master Boot Record (MBR). Each hard drive may only have a maximum of four primary partitions. One may only boot an OS from a primary partition. Extended partitions allow one to place up to 24 partitions on a single drive.
The above example shows the addition of a drive as one whole extended partition used to extend the storage space of the system. It was not created to hold additional operating systems as this would require a primary partition. Primary partitions can be used to extend the storage space of the system as well. It is not precluded from such a function but it will then limit you to four partitions for that hard drive.
--------------------------------------------------------------------------------
File: /etc/fstab
Enter the drive into the fstab file so that it is recognized and mounted upon system boot.
File: /etc/fstab Red Hat 8.0
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hda2 swap swap defaults 0 0
/dev/hdb1 /opt2 ext3 defaults 1 2
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0
The digits "1 2" refer to whether the mount point should be backed up when the dump command is used and disk integrity checks using fsck. The "1" states that it should be backed up when the dump command is issued (0=no). The "2" refers to the order in which "fsck" should check the mount points. The digit "1" identifies the root ("/") of the filesystem. All others should be "2". (0=no check)
Also see: fstab man page for a description of all options.
--------------------------------------------------------------------------------
Links
YoLinux Tutorial: System Administration - [Filesystems and drives]
YoLinux Tutorial: System optimization - Hard drive performance optimizations
Hard Drive Partitions - Definitions
Partitions - Tools, best practices, explanations
Man pages:
e2label - Add label to hard drive: e2label /dev/hdb EXTRA_DRIVE
Note: Labels support up to 16 characters.
fdisk - Manipulate/configure the partition table.
sfdisk - Manipulate/configure the partition table.
cfdisk - Curses based disk partition table manipulator.
mkfs - Build Linux file system. (Actually a front-end to various file system builders for various file system types.)
mke2fs - Create a Linux second extended file system.
tune2fs - Adjust file system parameters on a second extended filesystem. Convert ext2 to ext3, add volume label (-L), ...
mount - Mount a file system
fstab - Configuration file for mounting filesystems.
SCSI Drives:
Scsihosts - Kernel boot time module introduced in the stable release kernel 2.4. Controls SCSI device ordering.
Linux 2.4 SCSI subsystem HOWTO - [tldp]
YoLinux SCSI Info
Linux: Mount a Windows file system from Linux
Linux: Mount a Windows file system from Linux
--------------------------------------------------------------------------------
Question: How can I mount a Windows file system from Linux?
Answer: To mount a Windows file system from Linux can be a challenging task.
To begin, you'll need to determine what kind of Windows file system you are trying to view. Most flavors of Linux come with appropriate drivers for the most common file system types.
Windows 3.x, 95, 98, 98SE, and ME usually use a MSDOS or a VFAT formatted partition. (VFAT is a replacement file system, which is more efficient than the older MSDOS one.)
Windows NT4, 2000, and XP generally use a more advanced file system called NTFS.
All of the RedHat releases of Linux ship with support for the MSDOS and VFAT file systems. The newer NTFS file system is a different story. Very few of the Linux distributors ship with out-of-the-box support. This is for a good reason. While there is quite a bit known and published about MSDOS and VFAT, Microsoft has kept the specifics for NTFS very quiet, so the implementations vary in stability and features.
Fortunately, there is a web site which maintains RPM packages with appropriate NTFS drivers for most recent versions of RedHat Linux. The site can be found at:
http://linux-ntfs.sourceforge.net/info/redhat.html
If you are attempting to mount an NTFS file system, you'll need to download the appropriate RPM for your system. If you are unsure of how to do this or are confused by the next step, I would recommend that you seek more advanced Linux help. All systems are different so it is difficult to provide exact help with these types of problems.
To continue, you'll need to have determined what type of file system you have. If it is an NTFS file system, you will also need to have downloaded the correct RPM package from the site above and installed it without error.
Now that you have the necessary driver support installed, you'll need to determine which partition holds the Windows file system you need access to. You may already know this from your installation procedures.
Linux uses a different convention than Windows for describing disk partitions. A typical example of a Linux partition would be:
/dev/sda2
This indicates that you installed windows on your SCSI disk on the second partition.
An IDE hard drive would look something like:
/dev/hda2
If you have more than one hard disk in your computer, the convention will be different. For example, for the first partition on the second SCSI hard disk would take the form:
/dev/sdb1
Hopefully by now, you've determined where you installed your Windows file system.
Next, assuming an NTFS file system, try mounting the partition by typing something like:
mount -t ntfs /dev/sda1 /mnt (Of course replacing the /dev/sda1 with your partition specifics.)
This command should complete without error. If you get an error, you may either not have the file system driver installed correctly or the partition you specified may be incorrect.
For VFAT or MSDOS partitions, change the -t flag in the mount command to "vfat" or "msdos".
Accessing disk partitions is a very dangerous task and should be done with great care. If you have any trouble with the commands or concepts above, please ask an advanced Linux user to take a look at your system.
--------------------------------------------------------------------------------
Question: How can I mount a Windows file system from Linux?
Answer: To mount a Windows file system from Linux can be a challenging task.
To begin, you'll need to determine what kind of Windows file system you are trying to view. Most flavors of Linux come with appropriate drivers for the most common file system types.
Windows 3.x, 95, 98, 98SE, and ME usually use a MSDOS or a VFAT formatted partition. (VFAT is a replacement file system, which is more efficient than the older MSDOS one.)
Windows NT4, 2000, and XP generally use a more advanced file system called NTFS.
All of the RedHat releases of Linux ship with support for the MSDOS and VFAT file systems. The newer NTFS file system is a different story. Very few of the Linux distributors ship with out-of-the-box support. This is for a good reason. While there is quite a bit known and published about MSDOS and VFAT, Microsoft has kept the specifics for NTFS very quiet, so the implementations vary in stability and features.
Fortunately, there is a web site which maintains RPM packages with appropriate NTFS drivers for most recent versions of RedHat Linux. The site can be found at:
http://linux-ntfs.sourceforge.net/info/redhat.html
If you are attempting to mount an NTFS file system, you'll need to download the appropriate RPM for your system. If you are unsure of how to do this or are confused by the next step, I would recommend that you seek more advanced Linux help. All systems are different so it is difficult to provide exact help with these types of problems.
To continue, you'll need to have determined what type of file system you have. If it is an NTFS file system, you will also need to have downloaded the correct RPM package from the site above and installed it without error.
Now that you have the necessary driver support installed, you'll need to determine which partition holds the Windows file system you need access to. You may already know this from your installation procedures.
Linux uses a different convention than Windows for describing disk partitions. A typical example of a Linux partition would be:
/dev/sda2
This indicates that you installed windows on your SCSI disk on the second partition.
An IDE hard drive would look something like:
/dev/hda2
If you have more than one hard disk in your computer, the convention will be different. For example, for the first partition on the second SCSI hard disk would take the form:
/dev/sdb1
Hopefully by now, you've determined where you installed your Windows file system.
Next, assuming an NTFS file system, try mounting the partition by typing something like:
mount -t ntfs /dev/sda1 /mnt (Of course replacing the /dev/sda1 with your partition specifics.)
This command should complete without error. If you get an error, you may either not have the file system driver installed correctly or the partition you specified may be incorrect.
For VFAT or MSDOS partitions, change the -t flag in the mount command to "vfat" or "msdos".
Accessing disk partitions is a very dangerous task and should be done with great care. If you have any trouble with the commands or concepts above, please ask an advanced Linux user to take a look at your system.
I am going to divide each part as follows
I am going to divide each part as follows
1. Plan the layout of the filesystem with the new drive
2. Partition the new hard drive
3. Format the new partitions
4. Test the new space
5. Copy data from old to new partition (optional)
6. Edit /etc/fstab
7. Reboot
8. Remove old data (optional)
Here is the details about each one.
1. Plan the new filesystem. Where would you like to use the new space? Do
df
to print a summary of free/used space on each of the existing mounted partitions. Do
du
on selected directories to find their size.
For example, I would consider using new hard drive space in one of the following mount points:
/usr/local
/home
/home/share/downloads
/usr/local/mp3s
/usr/local/dos_data
Here is Details.
/usr/local is suposed to survive any upgrade of Linux. It is nice to have it on a separate partition because I can even reformat other partitions without affecting my local contents stored in /usr/local. I surely want it of the type "ext2" or perhaps "reiserfs".
/home contains user data. Surely, it is the data that deserves the most care. It is obviously supposed to survive any upgrade of Linux. Wow, obviously I want it on a separate partition. The type is normally "ext2" or "raiserfs".
/usr/local/mp3s is a non-standard Linux directory. I may keep my MP3 (music) files there. Those tend to be large.
/usr/local/dos_data. Another non-standard directory. If I dual boot, I would consider making an extra partion of the type "DOS FAT32" or similar so as to share files between MS Windows and Linux transparently (both ways). I would configure all the Windows-based programs to use this "drive" as the default location for all user-generated files. I could even have "mp3s", "cds" and other such directories in this location. The serious drawback of this approach--MS Windows may insist on messing up with this partion on re-install.
2. Partition the new hard drive. For example, if my new harddrive is the slave on the second IDE interface (perhaps the "fourth" IDE drive), I could use:
cfdisk /dev/hdd
or the more old-fashioned (and standard) tool:
fdisk /dev/hdd
If your drive is not "hdd" adjust the above command as needed.
hda -- first ide master (whole disk)
hdb -- first ide slave
hdc -- second ide master
hdd -- second ide slave
sda -- first scsi (whole disk)
sdb -- second scsi (whole disk)
...
sdp -- sixteenth scsi (whole disk)
For other disks, consult /usr/src/Linux/Documentation/devices.txt.
Most of the time, Linux partitions to be of the type ext2 ("Linux").
Partitioning can be tricky--if you never have done it, read man fdisk and man cfdisk. It is very easy to delete a partition with all your data. Make sure you know which disk you are working with!
fdisk or cfdisk does not make any changes to the hard drive until I write the new partition layout. So if I make a bad mistake, I can always quit without writing. I write the layout to the drive only when I am completely done.
3. Format each partition. For example, to format the first partition, while checking for bad blocks (-c), I would do:
mkfs -c -t ext2 /dev/hdd1
4. Test the new partitions around. Mount the new partitions manually (the mount directory must exist and be empty). Copy a bunch of files to each partition. View/edit a couple of random files. Delete them all.
5. Copy data. Optional--only if you would like to move data from an old partition to a new partition. Go to the single-user mode (init 1). Mount the new partition manually. Copy the data from the old partition to the new partition. Careful with the old data, you probably don't want to lose it if you made a mistake, so I wouldn't delete it yet--I rename the top level directory appropriately. E.g.,
cp -R /usr/local/ /mnt/hdd1/
mv /usr/local/ /usr/local.old.backup_of_2005-04-21
6. Edit the file /etc/fstab. Modify it to reflect your new filesystem layout. Perhaps, insert the mountpoint for the new partition(s) or modify any old mountpoints as needed. For example, if moving /usr/local to its own partition, I would need to add to add a line like this:
/dev/hdd1 /usr/local ext2 defaults 1 2
7. Reboot and test. The alternative to reboot is to unmount old and mount new mount points. For example:
umount /usr/local
mount -a
but hard reboot may be a more rigorous test of the new layout.
8. Remove old data. After a few days, when I have the confidence everything is really working fine
1. Plan the layout of the filesystem with the new drive
2. Partition the new hard drive
3. Format the new partitions
4. Test the new space
5. Copy data from old to new partition (optional)
6. Edit /etc/fstab
7. Reboot
8. Remove old data (optional)
Here is the details about each one.
1. Plan the new filesystem. Where would you like to use the new space? Do
df
to print a summary of free/used space on each of the existing mounted partitions. Do
du
on selected directories to find their size.
For example, I would consider using new hard drive space in one of the following mount points:
/usr/local
/home
/home/share/downloads
/usr/local/mp3s
/usr/local/dos_data
Here is Details.
/usr/local is suposed to survive any upgrade of Linux. It is nice to have it on a separate partition because I can even reformat other partitions without affecting my local contents stored in /usr/local. I surely want it of the type "ext2" or perhaps "reiserfs".
/home contains user data. Surely, it is the data that deserves the most care. It is obviously supposed to survive any upgrade of Linux. Wow, obviously I want it on a separate partition. The type is normally "ext2" or "raiserfs".
/usr/local/mp3s is a non-standard Linux directory. I may keep my MP3 (music) files there. Those tend to be large.
/usr/local/dos_data. Another non-standard directory. If I dual boot, I would consider making an extra partion of the type "DOS FAT32" or similar so as to share files between MS Windows and Linux transparently (both ways). I would configure all the Windows-based programs to use this "drive" as the default location for all user-generated files. I could even have "mp3s", "cds" and other such directories in this location. The serious drawback of this approach--MS Windows may insist on messing up with this partion on re-install.
2. Partition the new hard drive. For example, if my new harddrive is the slave on the second IDE interface (perhaps the "fourth" IDE drive), I could use:
cfdisk /dev/hdd
or the more old-fashioned (and standard) tool:
fdisk /dev/hdd
If your drive is not "hdd" adjust the above command as needed.
hda -- first ide master (whole disk)
hdb -- first ide slave
hdc -- second ide master
hdd -- second ide slave
sda -- first scsi (whole disk)
sdb -- second scsi (whole disk)
...
sdp -- sixteenth scsi (whole disk)
For other disks, consult /usr/src/Linux/Documentation/devices.txt.
Most of the time, Linux partitions to be of the type ext2 ("Linux").
Partitioning can be tricky--if you never have done it, read man fdisk and man cfdisk. It is very easy to delete a partition with all your data. Make sure you know which disk you are working with!
fdisk or cfdisk does not make any changes to the hard drive until I write the new partition layout. So if I make a bad mistake, I can always quit without writing. I write the layout to the drive only when I am completely done.
3. Format each partition. For example, to format the first partition, while checking for bad blocks (-c), I would do:
mkfs -c -t ext2 /dev/hdd1
4. Test the new partitions around. Mount the new partitions manually (the mount directory must exist and be empty). Copy a bunch of files to each partition. View/edit a couple of random files. Delete them all.
5. Copy data. Optional--only if you would like to move data from an old partition to a new partition. Go to the single-user mode (init 1). Mount the new partition manually. Copy the data from the old partition to the new partition. Careful with the old data, you probably don't want to lose it if you made a mistake, so I wouldn't delete it yet--I rename the top level directory appropriately. E.g.,
cp -R /usr/local/ /mnt/hdd1/
mv /usr/local/ /usr/local.old.backup_of_2005-04-21
6. Edit the file /etc/fstab. Modify it to reflect your new filesystem layout. Perhaps, insert the mountpoint for the new partition(s) or modify any old mountpoints as needed. For example, if moving /usr/local to its own partition, I would need to add to add a line like this:
/dev/hdd1 /usr/local ext2 defaults 1 2
7. Reboot and test. The alternative to reboot is to unmount old and mount new mount points. For example:
umount /usr/local
mount -a
but hard reboot may be a more rigorous test of the new layout.
8. Remove old data. After a few days, when I have the confidence everything is really working fine
Thursday, May 6, 2010
Troubleshooting a Database Tablespace Used(%) Alert problem [ID 403264.1]
Troubleshooting a Database Tablespace Used(%) Alert problem [ID 403264.1]
--------------------------------------------------------------------------------
Modified 07-JAN-2010 Type TROUBLESHOOTING Status PUBLISHED
In this Document
Purpose
Last Review Date
Instructions for the Reader
Troubleshooting Details
Background
Determining the type of alert that the problem is related to
Investigation steps for 10g and above Locally Managed Tablespaces
Investigation steps for pre-10g tablespaces and Dictionary Managed Tablespaces
References
--------------------------------------------------------------------------------
Applies to:
Oracle Server - Enterprise Edition - Version: 9.0.1.5
Enterprise Manager for RDBMS - Version: 10.1.0.2
Enterprise Manager Grid Control - Version: 10.1.0.2
Information in this document applies to any platform.
Purpose
This article intends to describe the steps necessary to troubleshoot a problem with a Database Tablespace Used(%) Metric in Enterprise Manager 10g (Grid Control or Database Control) that is either not raising or clearing when it should.
NOTE: For a summary of Oracle Recommended Patches For Tablespace Monitoring using the Tablespace Space Used % metric, refer to Note 849498.1
Last Review Date
January 7, 2010
Instructions for the Reader
A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.
Troubleshooting Details
Background
Beginning with the 10g Database, for Locally Managed Tablespaces, the Oracle Management Agent no longer raises its own alerts for Tablespace Used(%) metrics like it does for a 9i Database. Instead, raising/clearing of these alerts is the responsibility of the Database via its 'Server-Generated Alert System' (see NOTE 240965.1 10g NEW FEATURE on TABLESPACE ADVISORY). Enterprise Manager (Grid or DBControl) simply synchronizes itself with the state of the alert that is raised in the Database. Enterprise Manager still collects the metric data but only uses this data for historical reporting purposes, i.e the graphs in the console.
There are therefore 2 different mechanisms being used for raising and clearing Tablespace Used(%) alerts in Enterprise Manager and, before starting to troubleshoot why any given alert is not clearing or raising when expected the first step is to determine which type of alert we are dealing with.
Determining the type of alert that the problem is related to
1. If the tablespace is in a pre-10g database, follow the Investigation steps for pre-10g tablespaces and Dictionary Managed Tablespaces.
2. Run the following sql as a DBA user in sqlplus:
select extent_management
from dba_tablespaces
where tablespace_name = '&tablespace_name';
If the query returns 'LOCAL', follow the Investigation steps for 10g and above Locally Managed Tablespaces.
If the query returns 'DICTIONARY', follow the Investigation steps for pre-10g tablespaces and Dictionary Managed Tablespaces.
Investigation steps for 10g and above Locally Managed Tablespaces
1. Get the current data from the relevant database views
Perform the following step to determine if the information displayed by Enterprise Manager accurately reflects the values stored in the 10g Database. Query the database for outstanding alerts and specifically tablespace alerts by issuing the following SQL commands while logged on as the SYS user, spooling the output to a file. (This information will be very useful to Oracle Support should an SR be necessary):
-- QUERY 1: The following query shows the outstanding alerts that the RDBMS is aware of:
SELECT REASON
, METRIC_VALUE
, MESSAGE_TYPE
, TO_CHAR(CREATION_TIME,'DD-MON-YYYY HH24:MI:SS')
, HOST_ID
FROM SYS.DBA_OUTSTANDING_ALERTS;
-- QUERY 2: The following query shows the current thresholds settings for the RDBMS tablespace full metric:
SELECT METRICS_NAME
, WARNING_OPERATOR WARN_OP
, WARNING_VALUE WARN_VAL
, CRITICAL_OPERATOR CRIT_OP
, CRITICAL_VALUE CRIT_VAL
, OBJECT_TYPE OBJ_TYPE
, OBJECT_NAME OBJ_NAME
, STATUS
FROM SYS.DBA_THRESHOLDS
WHERE metrics_name LIKE ‘%Tablespace%’; -- Do not replace the string ‘Tablespace’
-- QUERY 3: The following query shows the current values for the Tablespace Used(%) metric from the perspective of the RDBMS:
SELECT TABLESPACE_NAME TBSP_NAME
, USED_SPACE
, TABLESPACE_SIZE TBSP_SIZE
, USED_PERCENT
FROM SYS.DBA_TABLESPACE_USAGE_METRICS;
2. If the output of QUERY1 shows that there is an outstanding alert in the RDBMS but this alert is not shown in Grid Control
2.1. Try a clearstate of the Agent while the agent is running. The RDBMS only attempts to inform Grid Control of an alert once. If the message is lost on the way to Grid Control for any reason the RDBMS will not try again. A clearstate tells the agents to check whether there are any tablespace full alerts, without the RDBMS resending the alert.
/bin/emctl clearstate agent
2.2 Check that the OEM_MONITOR role has been granted privileges to dequeue messages from SYS.ALERT_QUE. If this is not the case, the RDBMS will be sending the alerts to the ALERT_QUE for the Agent to pick up and send on to the OMS but the Agent will not have privileges to read from the QUE.
select grantee, dequeue_privilege from sys.queue_privileges where owner = 'SYS' and name = 'ALERT_QUE';
-- This should return:
GRANTEE DEQUEUE_PRIVILEGE
------------------------------ -----------------
OEM_MONITOR 1
-- If it does not, grant the privilege using the following SQL as the SYS user:
exec dbms_aqadm.grant_queue_privilege('dequeue','alert_que','OEM_MONITOR',false);
2.3 Check that the user specified in 'Monitoring Configuration' for the database targets (usually dbsnmp) has the role 'OEM_MONITOR' and that it is a DEFAULT role for that user (see NOTE 397680.1 Errors In Emagent.Trc: Pls-00201: Identifier 'Dbms_aqadm') .
select grantee
, default_role
from dba_role_privs
where granted_role = 'OEM_MONITOR';
2.4 Check that the Agent has registered with the Server Generated Alerts system.
select agent_name from SYSTEM.AQ$_INTERNET_AGENTS;
-- This should return at least a row that contains the hostname, agent port and sid of the database, just like the one highlighted in bold in the example output. The name of the agent contains the (possibly truncated) hostname of the Agent, the Agent port and the Database SID
AGENT_NAME
------------------------------
MYHOST_MYDOMA_3872_ORCL102
HAE_SUB
SCHEDULER$_EVENT_AGENT
SERVER_ALERT
-- If it the query results do not contain an entry for your agent/port/DB, try restarting the agent, it should re-register. If it does not, this is a good time to raise an SR with Oracle Customer Support (see step 4 below).
2.5 Check that the HOST_ID in dba_outstanding_alerts matches the MachineName property of the oracle_database target in targets.xml. If the two values do not match, this can break the chain of events that lead to the alert being raised in Grid Control. This cause is predominantly seen in RAC environments when the oracle_database targets have been discovered with the virtual hostname while the RAC database is raising alerts with the physical hostname.
If the values do not match, a workaround is to update targets.xml so that the oracle_database uses the value seen for HOST_ID in dba_outstanding_alerts for the MachineName property:
2.5.1 Update/sysman/emd/targets.xml (or //sysman/emd/targets.xml in a RAC env.), change the MachineName for the oracle_database target to the value that is used for HOST_ID in dba_outstanding_alerts
2.5.2 Reload the Agent and then perform a clearstate.
/bin/emctl reload agent
/bin/emctl clearstate agent
2.6 (RAC only). You may be experiencing a known issue (unpublished Bug 4572724) with RAC database targets where Alerts are not raised due to the rac_database target in targets.xml not having the AssocTargetInstance property.
The workaround for this issue is to go to the Monitoring Configuration page for the rac_database target in Grid Control and complete the configuration steps (even if the target is already configured) and then restart the agent.
3. If there is no outstanding alert in the RDBMS (QUERY 1 returns no relevant rows) but an alert is shown in Grid Control
Scenario 1 : Raise and Clear occuring within 1 second. Bug 5013368 SEVERITIES FOR SERVER GENERATED METRICS INCORRECTLY REJECTED
In this rare situation, documented in Bug 5013368 SEVERITIES FOR SERVER GENERATED METRICS INCORRECTLY REJECTED, the alert does not clear even though the clear message has made it into the repository. This happens when the RDBMS raises and clears the alert within one second. Because the repository tables that store the records of the raise and clear use a DATE column to store the timestamp recording when the raise and clear occurs, the raise and clear, as far as the repository is concerned, happened at the same time and therefore we cannot determine which came first. This results in the Database Instance: > All Metrics > Tablespace Space Used (%) page for the tablespace showing both the raise and the clear in the Alert History table but the Alert not actually clearing.
NOTE: You may not see the clear record by default unless you select an option under 'View Data' that covers the period of the raise and clear occurring.
Workaround: To avoid this problem from occurring, Edit the Metric via 'Metric and Policy Settings' and specify a 'Number of Occurrences' greater than 1.
NOTE: There is currently no way of clearing such alerts without manual intervention under the direction of support. Please raise an SR via My Oracle Support to progress such issues.
Scenario 2 : Clear record not making it to the repository. Bug 7046253 ORPHANED PUSH ALERTS (E.G TABLESPACE FULL) IN GRID CONTROL
The OMS has not received the message from the RBDMS, via the Agent, to clear the alert. The RDBMS sends the message only once and therefore the alert will not clear in Enterprise Manager without manual intervention if, for some reason, it has not managed to get to the OMS.
Workaround: Use emctl clearstate agent, while the agent is running, to resynchronize the RDBMS and the Agent.
Unpublished Bug 4222570 - fixed in 10.2 agents, allows the RDBMS and Agent/OMS to re-synchronize if they become out of synch. The fix to Bug 4222570 allows an 'emctl clearstate agent' to force a resynch and clear the alert.
Patch 4222570 is available for 10.1.0.4.0 agents.
Unpublished Bug 4923126 fixes a similar issue specific to RAC databases. This Bug is fixed in both 11.1 and 10.2.0.3.0 (and above) Agents
Patch 4923126 is available on limited platform/versions (the link will take you to My Oracle Support, where you can check the availability for your platform/Agent version).
NOTE: Unpublished Bug 5913097, now fixed and backported to selected platform/versions of the Agent, deals with the fact that an Agent clearstate will only resolve such issues if there is a record of the clear in dba_alert_history. Unfortunately, this information is timed out of dba_alert_history based on the AWR retention period. An agent that has PATCH 5913097 no longer requires a record of the clear to be in dba_alert_history for an Agent clearstate to clear the alert.
Use the following query to return relevant rows from dba_alert_history:
SELECT REASON
, TO_CHAR(CREATION_TIME,'dd-mon-yyy hh24:mi:ss') ctime
, TO_CHAR(TIME_SUGGESTED,'dd-mon-yyy hh24:mi:ss') rtime
FROM DBA_ALERT_HISTORY
WHERE OBJECT_TYPE = 'TABLESPACE'
AND UPPER(RESOLUTION) = 'CLEARED'
ORDER BY CREATION_TIME ASC
A record of a clear for a Tablespace Used(%) alert will have a REASON with the new threshold that is below the Warning or Critical threshold, e.g:
Tablespace [SYSTEM] is [25 percent] full
If it is clear that a tablespace full alert is not clearing for any of the 2 scenarios, above, check the current status of the relevant Bug. If there is no fix currently available and/or you need a patch for your specific platform/agent version, raise an SR with Oracle Support for further assistance.
4. If the view dba_tablespace_usage_metrics shows that the USED_PERCENT has crossed the threshold defined for your tablespace in DBA_THRESHOLDS but there is no alert record in dba_outstanding_alerts (and therefore, by definition, Grid Control) you may be hitting the following Bug:
Bug 7462407 TABLESPACE ALERT NOT TRIGGERED FOR 10.2.0.4.0 RAC DATABASE- Results in some tablespace alerts not being raised by the Server Generated Alert system after another tablespace (a tablespace other than the tablespace that the alert should have been raised for) has been dropped.
This Bug is fixed in version 12.1 and Patch 7462407 is available from My Oracle Support for selected platforms. If the patch is not available for your platform and database version, please raise an SR via My Oracle Support to request a backport.
NOTE 1: Despite the Abstract for this Bug, this is NOT specific to RAC databases.
NOTE 2: Bug 8898153 TABLESPACE ALERT NOT TRIGGERED FOR 10.2.0.4.0 RAC DATABASE has been raised to investigate this problem further as it seems that the original fix did not fix all instances of this problem. To verify whether you might be hitting this problem, issue the following SQL on the target database:
select ts#, name from v$tablespace order by ts#;
If you are hitting the problem, the problem tablespace will have a TS# above a 'gap' in the set of TS#. Alerts will be successfully raised and cleared for tablespaces below the 'gap', e.g:
SQL> select ts#, name from v$tablespace order by ts#;
TS# NAME
---------- ------------------------------
0 SYSTEM
1 UNDOTBS1
2 SYSAUX
3 TEMP
4 DATA01
6 DATA03
7 DATA04
In the example above, tablespaces SYSTEM, UNDOTBS1, SYSAUX, TEMP and DATA01 would raise and clear alerts successfully but tablespaces DATA03 and DATA04 would not.
Unpublished Bug 5245039 APPSST GSI 10G: TS SPACE USED % ALERT NOT TRIGGERED WHEN USED SPACE IS >320GB - Results in tablespaces that are over 320GB in size not triggering tablespace used (%) alerts.
This Bug is fixed in version 10.2.0.4.0 of the database and has been backported to 10.2.0.3.0. Patch 5245039 is available from My Oracle Support for selected platforms.
5. If the view dba_tablespace_usage_metrics (QUERY 3) does not return the value you expect for USED_PERCENT and, hence, no alert is being raised or an alert is raised when it should not be, you may be hitting one of the following Bugs:
Unpublished Bug 7660028 TS FULL (%) ALERT GENERATION DOES NOT CONSIDER AVAILABLE DISK FREE SPACE. Basically, this Bug deals with the fact that an unpatched Database Server does not take into account the amount of space that is on the filesystem when calculating the Tablespace used (%) but only considers how much the datafiles that are part of the tablespace can theoretically extend (assuming there is space on the filesystem).
For example (assuming the filesystem is used for nothing else other than the data file):
Tablespace TEST_TBS has 1 datafile with 2.5GB of space allocated to it
Tablespace TEST_TBS has 1.25GB of space used
The size of the filesystem that the datafile is created on is 5GB
- 2.5GB of space is available after the tablespace is created
If the Max File Size of the datafile is set to 5GB, USED_PERCENT will be reported correctly as 25%
If the Max File Size of the datafile is set to 10GB, USED_PERCENT will be reported incorrectly as 12.5%. This is because the calculation of USED_PERCENT assumes that the datafile can extend to 10GB even though there is only 2.5GB of disk space available and therefore the tablespace can only extend to 5GB. The 'Actual' USED_PERCENT should still be 25% as the tablespace can still only extend to 5GB.
Once Patch 7660028 is applied to the Database Server, USED_PERCENT is calculated taking into account the space available on the filesystem.
Bug 7250921 USED_PERCENT INCORRECT ON DBA_TABLESPACE_USAGE_METRICS FOR
PARTITIONED OBJECTS. This Bug deals with inaccurate values for USED_PERCENT, believed to be specific to tablespaces that have partitioned objects. - Duplicate of <<4685811>> USED PERCENT OF RBS TABLESPACE DOES NOT DECREASE PROPERLY WHEN SHRINK OCCURS
Bug 6629893 INCONSISTENCIES IN TABLESPACE USAGE CALCUALTION./ NOT GETTING TABLESPACE ALERTS. Patch 6629893 is available to fix this issue.
Unpublished Bug 5527591 TABLESPACE USAGE PERCENTAGE DIFFERS DEPENDING ON TABLES(VIEWS) USED. Fixed in 11g and backports available via Patch 5527591
Bug 4566763 VALUE FOR TS USED (%) IS INCONSISTENT FROM OBJECT SEARCH PAGE AND METRIC PAGE
Unpublished Bug 5549540 DBA_TABLESPACE_USAGE_METRICS USAGE SHOULD NOT INCLUD OBJECTS IN RECYCLE BIN. Fixed in 11g and backports available via Patch 5549540
Bug 4472437 USED PERCENT OF SYSTEM TABLESPACE DOES NOT INCREASE WITHOUT SHUTDOWN INSTANCE.. Fixed in 11g and backports available via PATCH 4472437
Bug 6759910 DBA_TABLESPACE_USAGE_METRICS USED_PERCENT SHOWS OVER 100%
6. If you have disabled the monitoring of a Tablespace and an Alert has not been cleared
See Note 392268.1 'How to - Exclude a Tablespace From The Tablespace Used (%)
Metric' for known issues with the disabling of tablespace monitoring'
7. If you have dropped a tablespace and an Alert is still showing in either dba_outstanding_alerts, Grid Control, or both
See Note 740340.1 'Metric Alerts are being Raised for Tablespaces Which no
Longer Exist / Dropped in the Database'
8. If the results from QUERY 2 show different thresholds than those that are reported in Grid Control
Cases have been seen where the thresholds configured in Grid Control have become out of sync. with the thresholds in the database targets's DBA_THRESHOLDS. When this is the case, alerts are always generated based on the values in DBA_THRESHOLDS and this can result in very confusing results in the Grid Control console with alerts raised even though the thresholds do not appear to have been crossed.
Bug 7163538 TABLESPACE SPACE USED THRESHOLDS NOT SYNCHRONIZED BETWEEN AGENT AND DATABASE, fixed in 10.2.0.5.0, provides the agent with a mechanism to automatically re-sync thresholds between the Agent and the target database at a configurable interval.
9. If none of the resolutions listed in steps 2 - 8 resolve your issue, raise an SR with Oracle Support
Upload the results of the queries in Step 1 and any evidence you collected while following this Note to the SR. Without this evidence, support will need to verify that all these known issues have been ruled out.
Upload an emagent.trc that shows the activity before and after issuing the command 'emctl clearstate agent'. Wait at least 15 minutes after issuing the clearstate command before uploading the files Because the emagent.trc files get cycled, this time period may be in an emagent.trc.n file. To be safe, simply upload all files that start with emagent.trc in/sysman/log (//sysman/log for RAC)
Set the property tracelevel.recvlets.aq=DEBUG and tracelevel.recvlets=DEBUG in/sysman/config/emd.properties (//sysman/config/emd.properties for RAC) then reload the agent to get more detailed trace information.
Investigation steps for pre-10g tablespaces and Dictionary Managed Tablespaces
1. Check the value of the problemTbsp(Tablespaces Full) metric for the tablespace using the Metrics Browser
Follow Note 276350.1 'How to Enable the Metrics Browser/Agent Browser for the Oracle Management Agent' to enable the Metric Browser for the agent.
Open the Metric Browser in a browser by going to the following URL:
http|https://:/emd/browser/main
Click on the database target and then on the problemTbsp(Tablespaces Full) link
2. If the value shown for the tablespace for pctUsed(Tablespace Space Used (%)) is incorrect for the tablespace concerned
The problem is Agent side. This means that the script that is used to return the Tablespace Space Used(%) values is not working correctly (or is not working as you expect it to at least) and should be investigated further by Oracle Customer Support. Examine the list of known issues below and if you cannot find and issue related to your problem, log an SR with Oracle Customer Support to investigate further. Upload a screenshot of the Metrics Browser to the SR. Unless there is an obvious error, explain why you believe the values to be incorrect. Also, upload the output of the following statements:
/bin/emctl status agent
/bin/emctl status agent_scheduler
3. If the value shown for the tablespace for pctUsed(Tablespace Space Used (%)) is correct for the tablespace concerned
The problem is related to the process of scheduling, collecting, uploading and processing the metric data and could be related to a problem either on the Agent side or on the OMS side.
3.1 Try a clearstate of the Agent
/bin/emctl clearstate agent
NOTE: Do not confuse a clearstate with a clean start of an Agent. A clearstate simply tells the Agent to re-evaluate all metrics. A clean start involves removing all state files (among other things) from the Agent and is potentially destructive. Do not perform a clean start of an Agent without a complete understanding/justification of why doing so will resolve your issue
3.2 If the alert does not raise/clear within 10 minutes of running a clearstate and the problem is not described in the list of known issues, below, raise an SR with Oracle Customer Support to investigate the issue further. Upload the output of the following command and refer to this Note to explain what you have done so far to troubleshoot the issue.
/bin/emctl status agent
4. Known Issues
Note 317261.1 Problem - Tablespace Metrics - Incorrect values for Tablespace full metric for 8i and 9i databases are firing Critical and Warning alerts.
References
BUG:4472437 - USED PERCENT OF SYSTEM TABLESPACE DOES NOT INCREASE WITHOUT SHUTDOWN INSTANCE.
BUG:4566763 - VALUE FOR TS USED (%) IS INCONSISTENT FROM OBJECT SEARCH PAGE AND METRIC PAGE
BUG:4685811 - USED PERCENT OF RBS TABLESPACE DOES NOT DECREASE PROPERLY WHEN SHRINK OCCURS
BUG:5013368 - SEVERITIES FOR SERVER GENERATED METRICS INCORRECTLY REJECTED
BUG:5734870 - SERVER ALERT THRESHOLDS NOT REMOVED WHEN TABLESPACE IS DROPPED
BUG:6629893 - INCONSISTENCIES IN TABLESPACE USAGE CALCUALTION./ NOT GETTING TABLESPACE ALERTS
BUG:6759910 - DBA_TABLESPACE_USAGE_METRICS USED_PERCENT SHOWS OVER 100%
BUG:7046253 - ORPHANED PUSH ALERTS (E.G TABLESPACE FULL) IN GRID CONTROL
BUG:7250921 - USED_PERCENT INCORRECT ON DBA_TABLESPACE_USAGE_METRICS FOR PARTITIONED OBJECTS
BUG:7593670 - DBA_TABLESPACE_USAGE_METRICS INCORRECT, NO ALERTS FIRE.
BUG:8898153 - TABLESPACE ALERT NOT TRIGGERED PROPERLY
NOTE:240965.1 - 10g NEW FEATURE on TABLESPACE ADVISORY
NOTE:317261.1 - Problem - Tablespace Metrics - Incorrect values for Tablespace full metric for 8i and 9i databases are firing Critical and Warning alerts.
NOTE:392268.1 - How to - Exclude a Tablespace From The Tablespace Used (%) Metric
NOTE:397680.1 - Errors In Emagent.Trc: Pls-00201: Identifier 'Dbms_aqadm'
NOTE:740340.1 - Metric Alerts are Raised by the Database for Tablespaces Which no Longer Exist / Dropped
NOTE:849498.1 - Oracle Recommended Patches For Tablespace Monitoring using the Tablespace Space Used % metric
--------------------------------------------------------------------------------
Modified 07-JAN-2010 Type TROUBLESHOOTING Status PUBLISHED
In this Document
Purpose
Last Review Date
Instructions for the Reader
Troubleshooting Details
Background
Determining the type of alert that the problem is related to
Investigation steps for 10g and above Locally Managed Tablespaces
Investigation steps for pre-10g tablespaces and Dictionary Managed Tablespaces
References
--------------------------------------------------------------------------------
Applies to:
Oracle Server - Enterprise Edition - Version: 9.0.1.5
Enterprise Manager for RDBMS - Version: 10.1.0.2
Enterprise Manager Grid Control - Version: 10.1.0.2
Information in this document applies to any platform.
Purpose
This article intends to describe the steps necessary to troubleshoot a problem with a Database Tablespace Used(%) Metric in Enterprise Manager 10g (Grid Control or Database Control) that is either not raising or clearing when it should.
NOTE: For a summary of Oracle Recommended Patches For Tablespace Monitoring using the Tablespace Space Used % metric, refer to Note 849498.1
Last Review Date
January 7, 2010
Instructions for the Reader
A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.
Troubleshooting Details
Background
Beginning with the 10g Database, for Locally Managed Tablespaces, the Oracle Management Agent no longer raises its own alerts for Tablespace Used(%) metrics like it does for a 9i Database. Instead, raising/clearing of these alerts is the responsibility of the Database via its 'Server-Generated Alert System' (see NOTE 240965.1 10g NEW FEATURE on TABLESPACE ADVISORY). Enterprise Manager (Grid or DBControl) simply synchronizes itself with the state of the alert that is raised in the Database. Enterprise Manager still collects the metric data but only uses this data for historical reporting purposes, i.e the graphs in the console.
There are therefore 2 different mechanisms being used for raising and clearing Tablespace Used(%) alerts in Enterprise Manager and, before starting to troubleshoot why any given alert is not clearing or raising when expected the first step is to determine which type of alert we are dealing with.
Determining the type of alert that the problem is related to
1. If the tablespace is in a pre-10g database, follow the Investigation steps for pre-10g tablespaces and Dictionary Managed Tablespaces.
2. Run the following sql as a DBA user in sqlplus:
select extent_management
from dba_tablespaces
where tablespace_name = '&tablespace_name';
If the query returns 'LOCAL', follow the Investigation steps for 10g and above Locally Managed Tablespaces.
If the query returns 'DICTIONARY', follow the Investigation steps for pre-10g tablespaces and Dictionary Managed Tablespaces.
Investigation steps for 10g and above Locally Managed Tablespaces
1. Get the current data from the relevant database views
Perform the following step to determine if the information displayed by Enterprise Manager accurately reflects the values stored in the 10g Database. Query the database for outstanding alerts and specifically tablespace alerts by issuing the following SQL commands while logged on as the SYS user, spooling the output to a file. (This information will be very useful to Oracle Support should an SR be necessary):
-- QUERY 1: The following query shows the outstanding alerts that the RDBMS is aware of:
SELECT REASON
, METRIC_VALUE
, MESSAGE_TYPE
, TO_CHAR(CREATION_TIME,'DD-MON-YYYY HH24:MI:SS')
, HOST_ID
FROM SYS.DBA_OUTSTANDING_ALERTS;
-- QUERY 2: The following query shows the current thresholds settings for the RDBMS tablespace full metric:
SELECT METRICS_NAME
, WARNING_OPERATOR WARN_OP
, WARNING_VALUE WARN_VAL
, CRITICAL_OPERATOR CRIT_OP
, CRITICAL_VALUE CRIT_VAL
, OBJECT_TYPE OBJ_TYPE
, OBJECT_NAME OBJ_NAME
, STATUS
FROM SYS.DBA_THRESHOLDS
WHERE metrics_name LIKE ‘%Tablespace%’; -- Do not replace the string ‘Tablespace’
-- QUERY 3: The following query shows the current values for the Tablespace Used(%) metric from the perspective of the RDBMS:
SELECT TABLESPACE_NAME TBSP_NAME
, USED_SPACE
, TABLESPACE_SIZE TBSP_SIZE
, USED_PERCENT
FROM SYS.DBA_TABLESPACE_USAGE_METRICS;
2. If the output of QUERY1 shows that there is an outstanding alert in the RDBMS but this alert is not shown in Grid Control
2.1. Try a clearstate of the Agent while the agent is running. The RDBMS only attempts to inform Grid Control of an alert once. If the message is lost on the way to Grid Control for any reason the RDBMS will not try again. A clearstate tells the agents to check whether there are any tablespace full alerts, without the RDBMS resending the alert.
2.2 Check that the OEM_MONITOR role has been granted privileges to dequeue messages from SYS.ALERT_QUE. If this is not the case, the RDBMS will be sending the alerts to the ALERT_QUE for the Agent to pick up and send on to the OMS but the Agent will not have privileges to read from the QUE.
select grantee, dequeue_privilege from sys.queue_privileges where owner = 'SYS' and name = 'ALERT_QUE';
-- This should return:
GRANTEE DEQUEUE_PRIVILEGE
------------------------------ -----------------
OEM_MONITOR 1
-- If it does not, grant the privilege using the following SQL as the SYS user:
exec dbms_aqadm.grant_queue_privilege('dequeue','alert_que','OEM_MONITOR',false);
2.3 Check that the user specified in 'Monitoring Configuration' for the database targets (usually dbsnmp) has the role 'OEM_MONITOR' and that it is a DEFAULT role for that user (see NOTE 397680.1 Errors In Emagent.Trc: Pls-00201: Identifier 'Dbms_aqadm') .
select grantee
, default_role
from dba_role_privs
where granted_role = 'OEM_MONITOR';
2.4 Check that the Agent has registered with the Server Generated Alerts system.
select agent_name from SYSTEM.AQ$_INTERNET_AGENTS;
-- This should return at least a row that contains the hostname, agent port and sid of the database, just like the one highlighted in bold in the example output. The name of the agent contains the (possibly truncated) hostname of the Agent, the Agent port and the Database SID
AGENT_NAME
------------------------------
MYHOST_MYDOMA_3872_ORCL102
HAE_SUB
SCHEDULER$_EVENT_AGENT
SERVER_ALERT
-- If it the query results do not contain an entry for your agent/port/DB, try restarting the agent, it should re-register. If it does not, this is a good time to raise an SR with Oracle Customer Support (see step 4 below).
2.5 Check that the HOST_ID in dba_outstanding_alerts matches the MachineName property of the oracle_database target in targets.xml. If the two values do not match, this can break the chain of events that lead to the alert being raised in Grid Control. This cause is predominantly seen in RAC environments when the oracle_database targets have been discovered with the virtual hostname while the RAC database is raising alerts with the physical hostname.
If the values do not match, a workaround is to update targets.xml so that the oracle_database uses the value seen for HOST_ID in dba_outstanding_alerts for the MachineName property:
2.5.1 Update
2.5.2 Reload the Agent and then perform a clearstate.
2.6 (RAC only). You may be experiencing a known issue (unpublished Bug 4572724) with RAC database targets where Alerts are not raised due to the rac_database target in targets.xml not having the AssocTargetInstance property.
The workaround for this issue is to go to the Monitoring Configuration page for the rac_database target in Grid Control and complete the configuration steps (even if the target is already configured) and then restart the agent.
3. If there is no outstanding alert in the RDBMS (QUERY 1 returns no relevant rows) but an alert is shown in Grid Control
Scenario 1 : Raise and Clear occuring within 1 second. Bug 5013368 SEVERITIES FOR SERVER GENERATED METRICS INCORRECTLY REJECTED
In this rare situation, documented in Bug 5013368 SEVERITIES FOR SERVER GENERATED METRICS INCORRECTLY REJECTED, the alert does not clear even though the clear message has made it into the repository. This happens when the RDBMS raises and clears the alert within one second. Because the repository tables that store the records of the raise and clear use a DATE column to store the timestamp recording when the raise and clear occurs, the raise and clear, as far as the repository is concerned, happened at the same time and therefore we cannot determine which came first. This results in the Database Instance:
NOTE: You may not see the clear record by default unless you select an option under 'View Data' that covers the period of the raise and clear occurring.
Workaround: To avoid this problem from occurring, Edit the Metric via 'Metric and Policy Settings' and specify a 'Number of Occurrences' greater than 1.
NOTE: There is currently no way of clearing such alerts without manual intervention under the direction of support. Please raise an SR via My Oracle Support to progress such issues.
Scenario 2 : Clear record not making it to the repository. Bug 7046253 ORPHANED PUSH ALERTS (E.G TABLESPACE FULL) IN GRID CONTROL
The OMS has not received the message from the RBDMS, via the Agent, to clear the alert. The RDBMS sends the message only once and therefore the alert will not clear in Enterprise Manager without manual intervention if, for some reason, it has not managed to get to the OMS.
Workaround: Use emctl clearstate agent, while the agent is running, to resynchronize the RDBMS and the Agent.
Unpublished Bug 4222570 - fixed in 10.2 agents, allows the RDBMS and Agent/OMS to re-synchronize if they become out of synch. The fix to Bug 4222570 allows an 'emctl clearstate agent' to force a resynch and clear the alert.
Patch 4222570 is available for 10.1.0.4.0 agents.
Unpublished Bug 4923126 fixes a similar issue specific to RAC databases. This Bug is fixed in both 11.1 and 10.2.0.3.0 (and above) Agents
Patch 4923126 is available on limited platform/versions (the link will take you to My Oracle Support, where you can check the availability for your platform/Agent version).
NOTE: Unpublished Bug 5913097, now fixed and backported to selected platform/versions of the Agent, deals with the fact that an Agent clearstate will only resolve such issues if there is a record of the clear in dba_alert_history. Unfortunately, this information is timed out of dba_alert_history based on the AWR retention period. An agent that has PATCH 5913097 no longer requires a record of the clear to be in dba_alert_history for an Agent clearstate to clear the alert.
Use the following query to return relevant rows from dba_alert_history:
SELECT REASON
, TO_CHAR(CREATION_TIME,'dd-mon-yyy hh24:mi:ss') ctime
, TO_CHAR(TIME_SUGGESTED,'dd-mon-yyy hh24:mi:ss') rtime
FROM DBA_ALERT_HISTORY
WHERE OBJECT_TYPE = 'TABLESPACE'
AND UPPER(RESOLUTION) = 'CLEARED'
ORDER BY CREATION_TIME ASC
A record of a clear for a Tablespace Used(%) alert will have a REASON with the new threshold that is below the Warning or Critical threshold, e.g:
Tablespace [SYSTEM] is [25 percent] full
If it is clear that a tablespace full alert is not clearing for any of the 2 scenarios, above, check the current status of the relevant Bug. If there is no fix currently available and/or you need a patch for your specific platform/agent version, raise an SR with Oracle Support for further assistance.
4. If the view dba_tablespace_usage_metrics shows that the USED_PERCENT has crossed the threshold defined for your tablespace in DBA_THRESHOLDS but there is no alert record in dba_outstanding_alerts (and therefore, by definition, Grid Control) you may be hitting the following Bug:
Bug 7462407 TABLESPACE ALERT NOT TRIGGERED FOR 10.2.0.4.0 RAC DATABASE- Results in some tablespace alerts not being raised by the Server Generated Alert system after another tablespace (a tablespace other than the tablespace that the alert should have been raised for) has been dropped.
This Bug is fixed in version 12.1 and Patch 7462407 is available from My Oracle Support for selected platforms. If the patch is not available for your platform and database version, please raise an SR via My Oracle Support to request a backport.
NOTE 1: Despite the Abstract for this Bug, this is NOT specific to RAC databases.
NOTE 2: Bug 8898153 TABLESPACE ALERT NOT TRIGGERED FOR 10.2.0.4.0 RAC DATABASE has been raised to investigate this problem further as it seems that the original fix did not fix all instances of this problem. To verify whether you might be hitting this problem, issue the following SQL on the target database:
select ts#, name from v$tablespace order by ts#;
If you are hitting the problem, the problem tablespace will have a TS# above a 'gap' in the set of TS#. Alerts will be successfully raised and cleared for tablespaces below the 'gap', e.g:
SQL> select ts#, name from v$tablespace order by ts#;
TS# NAME
---------- ------------------------------
0 SYSTEM
1 UNDOTBS1
2 SYSAUX
3 TEMP
4 DATA01
6 DATA03
7 DATA04
In the example above, tablespaces SYSTEM, UNDOTBS1, SYSAUX, TEMP and DATA01 would raise and clear alerts successfully but tablespaces DATA03 and DATA04 would not.
Unpublished Bug 5245039 APPSST GSI 10G: TS SPACE USED % ALERT NOT TRIGGERED WHEN USED SPACE IS >320GB - Results in tablespaces that are over 320GB in size not triggering tablespace used (%) alerts.
This Bug is fixed in version 10.2.0.4.0 of the database and has been backported to 10.2.0.3.0. Patch 5245039 is available from My Oracle Support for selected platforms.
5. If the view dba_tablespace_usage_metrics (QUERY 3) does not return the value you expect for USED_PERCENT and, hence, no alert is being raised or an alert is raised when it should not be, you may be hitting one of the following Bugs:
Unpublished Bug 7660028 TS FULL (%) ALERT GENERATION DOES NOT CONSIDER AVAILABLE DISK FREE SPACE. Basically, this Bug deals with the fact that an unpatched Database Server does not take into account the amount of space that is on the filesystem when calculating the Tablespace used (%) but only considers how much the datafiles that are part of the tablespace can theoretically extend (assuming there is space on the filesystem).
For example (assuming the filesystem is used for nothing else other than the data file):
Tablespace TEST_TBS has 1 datafile with 2.5GB of space allocated to it
Tablespace TEST_TBS has 1.25GB of space used
The size of the filesystem that the datafile is created on is 5GB
- 2.5GB of space is available after the tablespace is created
If the Max File Size of the datafile is set to 5GB, USED_PERCENT will be reported correctly as 25%
If the Max File Size of the datafile is set to 10GB, USED_PERCENT will be reported incorrectly as 12.5%. This is because the calculation of USED_PERCENT assumes that the datafile can extend to 10GB even though there is only 2.5GB of disk space available and therefore the tablespace can only extend to 5GB. The 'Actual' USED_PERCENT should still be 25% as the tablespace can still only extend to 5GB.
Once Patch 7660028 is applied to the Database Server, USED_PERCENT is calculated taking into account the space available on the filesystem.
Bug 7250921 USED_PERCENT INCORRECT ON DBA_TABLESPACE_USAGE_METRICS FOR
PARTITIONED OBJECTS. This Bug deals with inaccurate values for USED_PERCENT, believed to be specific to tablespaces that have partitioned objects. - Duplicate of <<4685811>> USED PERCENT OF RBS TABLESPACE DOES NOT DECREASE PROPERLY WHEN SHRINK OCCURS
Bug 6629893 INCONSISTENCIES IN TABLESPACE USAGE CALCUALTION./ NOT GETTING TABLESPACE ALERTS. Patch 6629893 is available to fix this issue.
Unpublished Bug 5527591 TABLESPACE USAGE PERCENTAGE DIFFERS DEPENDING ON TABLES(VIEWS) USED. Fixed in 11g and backports available via Patch 5527591
Bug 4566763 VALUE FOR TS USED (%) IS INCONSISTENT FROM OBJECT SEARCH PAGE AND METRIC PAGE
Unpublished Bug 5549540 DBA_TABLESPACE_USAGE_METRICS USAGE SHOULD NOT INCLUD OBJECTS IN RECYCLE BIN. Fixed in 11g and backports available via Patch 5549540
Bug 4472437 USED PERCENT OF SYSTEM TABLESPACE DOES NOT INCREASE WITHOUT SHUTDOWN INSTANCE.. Fixed in 11g and backports available via PATCH 4472437
Bug 6759910 DBA_TABLESPACE_USAGE_METRICS USED_PERCENT SHOWS OVER 100%
6. If you have disabled the monitoring of a Tablespace and an Alert has not been cleared
See Note 392268.1 'How to - Exclude a Tablespace From The Tablespace Used (%)
Metric' for known issues with the disabling of tablespace monitoring'
7. If you have dropped a tablespace and an Alert is still showing in either dba_outstanding_alerts, Grid Control, or both
See Note 740340.1 'Metric Alerts are being Raised for Tablespaces Which no
Longer Exist / Dropped in the Database'
8. If the results from QUERY 2 show different thresholds than those that are reported in Grid Control
Cases have been seen where the thresholds configured in Grid Control have become out of sync. with the thresholds in the database targets's DBA_THRESHOLDS. When this is the case, alerts are always generated based on the values in DBA_THRESHOLDS and this can result in very confusing results in the Grid Control console with alerts raised even though the thresholds do not appear to have been crossed.
Bug 7163538 TABLESPACE SPACE USED THRESHOLDS NOT SYNCHRONIZED BETWEEN AGENT AND DATABASE, fixed in 10.2.0.5.0, provides the agent with a mechanism to automatically re-sync thresholds between the Agent and the target database at a configurable interval.
9. If none of the resolutions listed in steps 2 - 8 resolve your issue, raise an SR with Oracle Support
Upload the results of the queries in Step 1 and any evidence you collected while following this Note to the SR. Without this evidence, support will need to verify that all these known issues have been ruled out.
Upload an emagent.trc that shows the activity before and after issuing the command 'emctl clearstate agent'. Wait at least 15 minutes after issuing the clearstate command before uploading the files Because the emagent.trc files get cycled, this time period may be in an emagent.trc.n file. To be safe, simply upload all files that start with emagent.trc in
Set the property tracelevel.recvlets.aq=DEBUG and tracelevel.recvlets=DEBUG in
Investigation steps for pre-10g tablespaces and Dictionary Managed Tablespaces
1. Check the value of the problemTbsp(Tablespaces Full) metric for the tablespace using the Metrics Browser
Follow Note 276350.1 'How to Enable the Metrics Browser/Agent Browser for the Oracle Management Agent' to enable the Metric Browser for the agent.
Open the Metric Browser in a browser by going to the following URL:
http|https://
Click on the database target and then on the problemTbsp(Tablespaces Full) link
2. If the value shown for the tablespace for pctUsed(Tablespace Space Used (%)) is incorrect for the tablespace concerned
The problem is Agent side. This means that the script that is used to return the Tablespace Space Used(%) values is not working correctly (or is not working as you expect it to at least) and should be investigated further by Oracle Customer Support. Examine the list of known issues below and if you cannot find and issue related to your problem, log an SR with Oracle Customer Support to investigate further. Upload a screenshot of the Metrics Browser to the SR. Unless there is an obvious error, explain why you believe the values to be incorrect. Also, upload the output of the following statements:
3. If the value shown for the tablespace for pctUsed(Tablespace Space Used (%)) is correct for the tablespace concerned
The problem is related to the process of scheduling, collecting, uploading and processing the metric data and could be related to a problem either on the Agent side or on the OMS side.
3.1 Try a clearstate of the Agent
NOTE: Do not confuse a clearstate with a clean start of an Agent. A clearstate simply tells the Agent to re-evaluate all metrics. A clean start involves removing all state files (among other things) from the Agent and is potentially destructive. Do not perform a clean start of an Agent without a complete understanding/justification of why doing so will resolve your issue
3.2 If the alert does not raise/clear within 10 minutes of running a clearstate and the problem is not described in the list of known issues, below, raise an SR with Oracle Customer Support to investigate the issue further. Upload the output of the following command and refer to this Note to explain what you have done so far to troubleshoot the issue.
4. Known Issues
Note 317261.1 Problem - Tablespace Metrics - Incorrect values for Tablespace full metric for 8i and 9i databases are firing Critical and Warning alerts.
References
BUG:4472437 - USED PERCENT OF SYSTEM TABLESPACE DOES NOT INCREASE WITHOUT SHUTDOWN INSTANCE.
BUG:4566763 - VALUE FOR TS USED (%) IS INCONSISTENT FROM OBJECT SEARCH PAGE AND METRIC PAGE
BUG:4685811 - USED PERCENT OF RBS TABLESPACE DOES NOT DECREASE PROPERLY WHEN SHRINK OCCURS
BUG:5013368 - SEVERITIES FOR SERVER GENERATED METRICS INCORRECTLY REJECTED
BUG:5734870 - SERVER ALERT THRESHOLDS NOT REMOVED WHEN TABLESPACE IS DROPPED
BUG:6629893 - INCONSISTENCIES IN TABLESPACE USAGE CALCUALTION./ NOT GETTING TABLESPACE ALERTS
BUG:6759910 - DBA_TABLESPACE_USAGE_METRICS USED_PERCENT SHOWS OVER 100%
BUG:7046253 - ORPHANED PUSH ALERTS (E.G TABLESPACE FULL) IN GRID CONTROL
BUG:7250921 - USED_PERCENT INCORRECT ON DBA_TABLESPACE_USAGE_METRICS FOR PARTITIONED OBJECTS
BUG:7593670 - DBA_TABLESPACE_USAGE_METRICS INCORRECT, NO ALERTS FIRE.
BUG:8898153 - TABLESPACE ALERT NOT TRIGGERED PROPERLY
NOTE:240965.1 - 10g NEW FEATURE on TABLESPACE ADVISORY
NOTE:317261.1 - Problem - Tablespace Metrics - Incorrect values for Tablespace full metric for 8i and 9i databases are firing Critical and Warning alerts.
NOTE:392268.1 - How to - Exclude a Tablespace From The Tablespace Used (%) Metric
NOTE:397680.1 - Errors In Emagent.Trc: Pls-00201: Identifier 'Dbms_aqadm'
NOTE:740340.1 - Metric Alerts are Raised by the Database for Tablespaces Which no Longer Exist / Dropped
NOTE:849498.1 - Oracle Recommended Patches For Tablespace Monitoring using the Tablespace Space Used % metric
Database Partitioning for the E-Business Suite
New Whitepaper: Database Partitioning for the E-Business Suite
By Steven Chan on May 28, 2008 12:13 AM
Some readers complain that we don't have sufficient documentation to cover all possible scenarios and topics of interest. This is a valid observation. As your E-Business Suite deployments grow in complexity and scope, keeping ahead of your questions and new requirements is a constant challenge.
In my position as the editor of this blog, something I do only in my so-called free time, my situation is the odd inverse of yours, namely: the rate at which we release new Metalink Notes far-outstrips my capacity to read and announce them to the world. Here's a much-belated announcement about a database partitioning whitepaper produced by our Applications Performance Group.
What Is Database Partitioning?
Partitioning allows a single database table and its associated indexes to be broken into smaller components depending on the table and choice of index partitioning methods. Several E-Business Suite modules take advantage of database partitioning right out of the box, and custom partitioning is also fully supported. I've covered database partitioning concepts for Apps environments in more depth in this older article.
Best Practices for Partitioning Apps Databases
As I've noted before, we have a group in our Applications Development division that's dedicated to optimizing the E-Business Suite's performance. As a member of this Applications Performance group, Mohsin Sameen has worked extensively with some of our enterprise-class customers -- including many of the largest companies in the world -- on fine-tuning the performance of of their high-volume Apps environments.
Mohsin has distilled these experiences into an extensive and in-depth paper on database partitioning:
Database Partitioning for Oracle E-Business Suite (Metalink Note 554539.1)
Mohsin's excellent whitepaper covers topics such as:
Overview of database partitioning concepts
Table partitioning strategies involving range, list, hash, composite, and multi-column partitions
Index partitioning methods, including global and local partitioned indexes
Step-by-step decision framework for using partitions
Partition maintenance operations
Partitioning case study
The knee-jerk reaction answer to a performance problem is often to throw more hardware at it. If you have a large E-Business Suite environment where the growth rate of your historical transactional data is starting to affect performance, I'd strongly recommend reading this whitepaper. It's entirely possible that you could use it to squeeze some additional performance out of your existing environment without the added expense of new hardware.
Related Articles
Using Database Partitioning with the E-Business Suite
Performance Tuning for the E-Business Suite
Performance Tuning the Apps Database Layer
Master Class in Apps 11i Performance Tuning
Partitioning and Purging Best Practices for Oracle E-Business Suite
By Steven Chan on May 28, 2008 12:13 AM
Some readers complain that we don't have sufficient documentation to cover all possible scenarios and topics of interest. This is a valid observation. As your E-Business Suite deployments grow in complexity and scope, keeping ahead of your questions and new requirements is a constant challenge.
In my position as the editor of this blog, something I do only in my so-called free time, my situation is the odd inverse of yours, namely: the rate at which we release new Metalink Notes far-outstrips my capacity to read and announce them to the world. Here's a much-belated announcement about a database partitioning whitepaper produced by our Applications Performance Group.
What Is Database Partitioning?
Partitioning allows a single database table and its associated indexes to be broken into smaller components depending on the table and choice of index partitioning methods. Several E-Business Suite modules take advantage of database partitioning right out of the box, and custom partitioning is also fully supported. I've covered database partitioning concepts for Apps environments in more depth in this older article.
Best Practices for Partitioning Apps Databases
As I've noted before, we have a group in our Applications Development division that's dedicated to optimizing the E-Business Suite's performance. As a member of this Applications Performance group, Mohsin Sameen has worked extensively with some of our enterprise-class customers -- including many of the largest companies in the world -- on fine-tuning the performance of of their high-volume Apps environments.
Mohsin has distilled these experiences into an extensive and in-depth paper on database partitioning:
Database Partitioning for Oracle E-Business Suite (Metalink Note 554539.1)
Mohsin's excellent whitepaper covers topics such as:
Overview of database partitioning concepts
Table partitioning strategies involving range, list, hash, composite, and multi-column partitions
Index partitioning methods, including global and local partitioned indexes
Step-by-step decision framework for using partitions
Partition maintenance operations
Partitioning case study
The knee-jerk reaction answer to a performance problem is often to throw more hardware at it. If you have a large E-Business Suite environment where the growth rate of your historical transactional data is starting to affect performance, I'd strongly recommend reading this whitepaper. It's entirely possible that you could use it to squeeze some additional performance out of your existing environment without the added expense of new hardware.
Related Articles
Using Database Partitioning with the E-Business Suite
Performance Tuning for the E-Business Suite
Performance Tuning the Apps Database Layer
Master Class in Apps 11i Performance Tuning
Partitioning and Purging Best Practices for Oracle E-Business Suite
Installation and Diagnostics notes available related to the Oracle E-Business Suite Technology stack
Applies to:
Oracle Applications Technology Stack - Version: 11.5.10.2 to 12.0.6
Information in this document applies to any platform.
Goal
This note is to list the main Setup, Installation and Diagnostics notes available related to the Oracle E-Business Suite Technology stack.
Solution
Java
----------------------------------------------------------------------------------------------------
note 418664.1 Overview of Using Java with Oracle E-Business Suite Release 12
note 455492.1 Using Latest Update of Java 6.0 with Oracle E-Business Suite Release 12
note 384249.1 Using Latest Update of JDK 5.0 with Oracle E-Business Suite Release 12
note 300482.1 Overview of Using Java with Oracle E-Business Suite Release 11i
note 401561.1 Using J2SE Version 6 with Oracle E-Business Suite 11i
note 304099.1 Using J2SE Version 5.0 with Oracle E-Business Suite 11i, Release 11.5.10
note 246105.1 Upgrading to J2SE 1.4.2 with Oracle Applications 11i
note 130091.1 Upgrading Oracle Applications 11i to use JDK 1.3
JRE/Jinitiator
----------------------------------------------------------------------------------------------------
note 389422.1 Recommended Browsers for Oracle E-Business Suite Release 12
note 393931.1 Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12
note 285218.1 Recommended Browsers for Oracle Applications 11i
note 290807.1 Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i
note 124606.1 Upgrading JInitiator with Oracle E-Business Suite 11i
Forms
----------------------------------------------------------------------------------------------------
note 437878.1 Upgrading OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12
note 750359.1 Upgrading to Previous Version of OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12
note 384241.1 Using Forms Socket Mode with Oracle E-Business Suite Release 12
note 438652.1 R12 Forms Runtime Diagnostics (FRD), Tracing And Logging For Forms In Oracle Applications
note 125767.1 Upgrading Developer 6i with Oracle Applications 11i
note 232313.1 Information on Previous Versions of Developer 6i Patchsets
note 201340.1 Using Forms Listener Servlet with Oracle Applications 11i
note 150168.1 Obtaining Forms Runtime Diagnostics (FRD) In Oracle Applications 11i
note 760250.1 Diagnosing Forms Mouse Focus Problems Using JRE in Release 11i
OracleAS
----------------------------------------------------------------------------------------------------
note 454811.1 Upgrading to the Latest OracleAS 10g 10.1.3.x Patch Set in Oracle E-Business Suite Release 12
note 743518.1 Starting up AS10g services in an EBusiness Suite Release 12 environment
JDBC
----------------------------------------------------------------------------------------------------
note 557194.1 monitor_jdbc_conn.sql - Script to monitor JDBC connections in Apps eBusiness Suite
JVM
----------------------------------------------------------------------------------------------------
note 362851.1 Guidelines to setup the JVM in Apps Ebusiness Suite 11i and R12
note 567551.1 Configuring various JVM tuning parameters for Oracle E-Business suite 11i and R12
note 370583.1 Basic troubleshooting of JVM consuming cpu or too many JDBC connections in Apps 11i
Apache/mod_jserv
----------------------------------------------------------------------------------------------------
note 230688.1 11i Basic Apache/mod_jserv Troubleshooting with Hello.class
Debug/Trace
----------------------------------------------------------------------------------------------------
note 422419.1 R12 - How To Enable and Collect Debug for HTTP, OC4J and OPMN
Note 443671.1 R12 - Collecting Configuration Information for HTTP, OC4J and OPMN
note 427848.1 How to Enable Execution Context ID (ECID) in the R12 access_log
note 455154.1 R12: How To Obtain A Thread Dump When OC4J is shutdown
note 603390.1 How To Create a User Event Trace in R11i / R12
OA Framework
----------------------------------------------------------------------------------------------------
note 391554.1 Oracle Application Framework Documentation Resources, Release 12
note 275880.1 Oracle Application Framework Release 11i Documentation Road Map
note 275875.1 Oracle Application Framework Troubleshooting Release 11i (11.5.10)
note 357597.1 How To Generate A SQL Trace In OA Framework For Oracle Applications
WebCache
----------------------------------------------------------------------------------------------------
note 380486.1 Installing and Configuring Web Cache 10g and Oracle E-Business Suite 12
note 306653.1 Installing and Configuring Web Cache 10.1.2 and Oracle E-Business Suite 11i
JDeveloper
----------------------------------------------------------------------------------------------------
note 330236.1 Configuring JDeveloper For Use With Oracle Applications 11i and R12
note 357218.1 Troubleshooting JDeveloper setup for Oracle Applications
note 787209.1 How to find the correct version of JDeveloper to use with eBusiness Suite 11i or Release 12
Performance
----------------------------------------------------------------------------------------------------
note 163208.1 bde_last_analyzed.sql - Verifies CBO Statistics
note 174605.1 bde_chk_cbo.sql - Reports Database Initialization Parameters related to an Apps 12 or 11i instance
note 396009.1 Database Initialization Parameters for Oracle Applications Release 12
note 216205.1 Database Initialization Parameters for Oracle Applications 11i
note 744143.1 Tuning performance on eBusiness suite
note 169935.1 Troubleshooting Oracle Applications Performance Issues
note 244040.1 Oracle E-Business Suite Recommended Performance Patches
Security
----------------------------------------------------------------------------------------------------
note 738923.1 Oracle E-Business Suite Releases 11i and 12 Critical Patch Update note (January 2009)
note 403537.1 Best Practices for Securing Oracle E-Business Suite Release 12
note 189367.1 Best Practices for Securing the E-Business Suite Release 11i
Ihelp
----------------------------------------------------------------------------------------------------
Note 740834.1 R12: Troubleshooting iHelp
Advanced Configurations
----------------------------------------------------------------------------------------------------
note 380483.1 Oracle E-Business Suite Release 12 Additional Configuration and Deployment Options
note 384248.1 Sharing The Application Tier File System in Oracle E-Business Suite Release 12
note 217368.1 Advanced Configurations and Topologies for Enterprise Deployments of E-Business Suite 11i
note 233428.1 Sharing the Application Tier File System in Oracle Applications 11i
note 233436.1 Installing Oracle Application Server 10g with Oracle E-Business Suite Release 11i
note 364439.1 Tips and Queries for Troubleshooting Advanced Topologies
DMZ
----------------------------------------------------------------------------------------------------
note 380490.1 Oracle E-Business Suite R12 Configuration in a DMZ
note 726953.1 Case History: Implementing a Reverse Proxy Alone in the DMZ Configuration - R12
note 287176.1 DMZ Configuration with Oracle E-Business Suite 11i
note 438744.1 Case History: Implementing a Reverse Proxy Alone in a DMZ Configuration - 11i
note 460564.1 Hints and Tips for Troubleshooting the URL Firewal
Loadbalancer
----------------------------------------------------------------------------------------------------
note 380489.1 Using Load-Balancers with Oracle E-Business Suite Release 12
note 727171.1 Implementing Load Balancing On Oracle E-Business Suite - Documentation For Specific Load Balancer Hardware
note 601694.1 How To Check Session Persistence On BigIP F5 And Cisco Ace Load Balancer Appliances
note 603325.1 Using Cisco ACE Series Application Control Engine with Oracle E-Business Suite Release 12
SSL
----------------------------------------------------------------------------------------------------
note 376700.1 Using SSL with Oracle E-Business Suite Release 12
note 123718.1 11i A Guide to Understanding and Implementing SSL for Oracle Applications
Portal
----------------------------------------------------------------------------------------------------
note 305918.1 Using Oracle Portal 10g with Oracle E-Business Suite Release 11i
SSO/OID
----------------------------------------------------------------------------------------------------
note 376811.1 Integrating Oracle E-Business Suite Release 12 with 10g AS Oracle Internet Directory and Oracle Single Sign-On
note 261914.1 Integrating Oracle E-Business Suite Release 11i with Oracle Internet Directory and Oracle Single Sign-On
note 444573.1 Basic checks for user integration when using Oracle E-Business Suite 11i with Oracle AS 10g
Orace Access Manager / AccessGate
----------------------------------------------------------------------------------------------------
note 975182.1 Integrating Oracle E-Business Suite with Oracle Access Manager using Oracle E-Business Suite AccessGate
note 1077460.1 Troubleshooting Oracle Access Manager and Oracle E-Business Suite AccessGate
Webcenter
----------------------------------------------------------------------------------------------------
note 557221.1 Oracle WebCenter 10g Application Creation and Deployment Guide for Oracle E-Business Suite Release 12
Secure Enterprise Search
----------------------------------------------------------------------------------------------------
note.566097.1 Oracle E-Business Suite Secure Enterprise Search Release Notes, Release 12.1.1
note.744820.1 Oracle E-Business Suite Secure Enterprise Search Best Practices, Release 12
note.462377.1 Installing Oracle E-Business Suite Secure Enterprise Search, Release 12
note.740499.1 Oracle E-Business Suite Secure Enterprise Search Release Notes, Release 12.0.6
note 726239.1 Oracle E-Business Suite Secure Enterprise Search Troubleshooting Guidelines, Release 12
SOA/BPEL/Webservices
----------------------------------------------------------------------------------------------------
note 556540.1 Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.1
note 565922.1 Oracle E-Business Suite Integrated SOA Gateway Release Notes, Release 12.1.1
note 815196.1 Oracle E-Business Suite Integrated SOA Gateway 12.1.1 Consolidated One-Off
note 726414.1 Oracle E-Business Suite Integrated SOA Gateway Troubleshooting Guide, Release 12
note 755067.1 Using Oracle BPEL 10g with E-Business Suite Release 12.1.1
note 755069.1 EBS R12 Packager and Adapters for External Application Servers
Note 782455.1 How Can I Expose E-Business Suite Integration Interfaces as Web Services in Release 11i and R12.0
MWA
----------------------------------------------------------------------------------------------------
note 782162.1 MWA Troubleshooting Tips for Release 12
note 269991.1 MWA Troubleshooting Tips for Release 11i
Certified/Supported
----------------------------------------------------------------------------------------------------
http://blogs.oracle.com/stevenchan/certifications.html
note 363827.1 Rebaselined Oracle Applications Technology Components for Releases 11.5.7, 11.5.8, 11.5.9, and 11.5.10
note 883202.1 Minimum Baseline Patch Requirements for Extended Support on Oracle E-Business Suite 11.5.10
WEBADI
----------------------------------------------------------------------------------------------------
note 417692.1 Installing, Configuring and Troubleshooting Web ADI (Web Applications Desktop Integrator)
note 452452.1 R12 Installing, Configuring and Troubleshooting Web ADI (Web Applications Desktop Integrator)
note 294739.1 How to enable tracing for WEBADI
note 726989.1 List of Patches in Web Applications Desktop Integrator (Web ADI) for Releases 11i and 12
Diagnostics
----------------------------------------------------------------------------------------------------
note 167000.1 E-Business Suite Diagnostics Installation Guide
note 421245.1 E-Business Suite Diagnostics References for R12
note 179661.1 E-Business Suite Diagnostics 11i Test Catalog
Installation
----------------------------------------------------------------------------------------------------
note 761564.1 Oracle Applications Installation and Upgrade Notes Release 12 (12.1.1) for Linux x86
note 402310.1 Oracle Applications Installation and Upgrade notes Release 12 (12.0) for Linux (32-bit)
note 406982.1 Cloning Oracle Applications Release 12 with Rapid Clone
note 559518.1 Cloning Oracle E-Business Suite Release 12 RAC-Enabled Systems with Rapid Clone
note 421409.1 Unbreakable Linux enviroment check before R12 install
note 458533.1 How to Enable Enterprise Manager on the Oracle E-Business Suite Release 12
note 603716.1 Using AS10g AS Control with eBusiness Suite Rel 12
note 452120.1 How to locate the log files and troubleshoot RapidWiz for R12
note 316806.1 Oracle Applications Installation Update notes, Release 11i (11.5.10.2)
note:230672.1 Cloning Oracle Applications Release 11i with Rapid Clone
note 207296.1 How to Find out Linux Version Information?
Database
----------------------------------------------------------------------------------------------------
note:454750.1 Oracle Apps Release 12 with Oracle Database 10.2.0 interoperability notes
note 735276.1 Interoperability notes E-Business Suite R12 with Oracle Database 11gR1
note 388577.1 Configuring Oracle Applications Release 12 with 10g R2 RAC
note 466649.1 Using Oracle 11g Release 1 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12
note 216550.1 Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0)
note 362203.1 Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0)
note 452783.1 Oracle Applications Release 11i with Oracle 11g Release 1 (11.1.0)
note 362135.1 Configuring Oracle Applications Release 11i with 10g R2 RAC and ASM
note 554539.1 Using Database Partitioning with Oracle E-Business Suite
Oracle Applications Technology Stack - Version: 11.5.10.2 to 12.0.6
Information in this document applies to any platform.
Goal
This note is to list the main Setup, Installation and Diagnostics notes available related to the Oracle E-Business Suite Technology stack.
Solution
Java
----------------------------------------------------------------------------------------------------
note 418664.1 Overview of Using Java with Oracle E-Business Suite Release 12
note 455492.1 Using Latest Update of Java 6.0 with Oracle E-Business Suite Release 12
note 384249.1 Using Latest Update of JDK 5.0 with Oracle E-Business Suite Release 12
note 300482.1 Overview of Using Java with Oracle E-Business Suite Release 11i
note 401561.1 Using J2SE Version 6 with Oracle E-Business Suite 11i
note 304099.1 Using J2SE Version 5.0 with Oracle E-Business Suite 11i, Release 11.5.10
note 246105.1 Upgrading to J2SE 1.4.2 with Oracle Applications 11i
note 130091.1 Upgrading Oracle Applications 11i to use JDK 1.3
JRE/Jinitiator
----------------------------------------------------------------------------------------------------
note 389422.1 Recommended Browsers for Oracle E-Business Suite Release 12
note 393931.1 Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12
note 285218.1 Recommended Browsers for Oracle Applications 11i
note 290807.1 Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i
note 124606.1 Upgrading JInitiator with Oracle E-Business Suite 11i
Forms
----------------------------------------------------------------------------------------------------
note 437878.1 Upgrading OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12
note 750359.1 Upgrading to Previous Version of OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12
note 384241.1 Using Forms Socket Mode with Oracle E-Business Suite Release 12
note 438652.1 R12 Forms Runtime Diagnostics (FRD), Tracing And Logging For Forms In Oracle Applications
note 125767.1 Upgrading Developer 6i with Oracle Applications 11i
note 232313.1 Information on Previous Versions of Developer 6i Patchsets
note 201340.1 Using Forms Listener Servlet with Oracle Applications 11i
note 150168.1 Obtaining Forms Runtime Diagnostics (FRD) In Oracle Applications 11i
note 760250.1 Diagnosing Forms Mouse Focus Problems Using JRE in Release 11i
OracleAS
----------------------------------------------------------------------------------------------------
note 454811.1 Upgrading to the Latest OracleAS 10g 10.1.3.x Patch Set in Oracle E-Business Suite Release 12
note 743518.1 Starting up AS10g services in an EBusiness Suite Release 12 environment
JDBC
----------------------------------------------------------------------------------------------------
note 557194.1 monitor_jdbc_conn.sql - Script to monitor JDBC connections in Apps eBusiness Suite
JVM
----------------------------------------------------------------------------------------------------
note 362851.1 Guidelines to setup the JVM in Apps Ebusiness Suite 11i and R12
note 567551.1 Configuring various JVM tuning parameters for Oracle E-Business suite 11i and R12
note 370583.1 Basic troubleshooting of JVM consuming cpu or too many JDBC connections in Apps 11i
Apache/mod_jserv
----------------------------------------------------------------------------------------------------
note 230688.1 11i Basic Apache/mod_jserv Troubleshooting with Hello.class
Debug/Trace
----------------------------------------------------------------------------------------------------
note 422419.1 R12 - How To Enable and Collect Debug for HTTP, OC4J and OPMN
Note 443671.1 R12 - Collecting Configuration Information for HTTP, OC4J and OPMN
note 427848.1 How to Enable Execution Context ID (ECID) in the R12 access_log
note 455154.1 R12: How To Obtain A Thread Dump When OC4J is shutdown
note 603390.1 How To Create a User Event Trace in R11i / R12
OA Framework
----------------------------------------------------------------------------------------------------
note 391554.1 Oracle Application Framework Documentation Resources, Release 12
note 275880.1 Oracle Application Framework Release 11i Documentation Road Map
note 275875.1 Oracle Application Framework Troubleshooting Release 11i (11.5.10)
note 357597.1 How To Generate A SQL Trace In OA Framework For Oracle Applications
WebCache
----------------------------------------------------------------------------------------------------
note 380486.1 Installing and Configuring Web Cache 10g and Oracle E-Business Suite 12
note 306653.1 Installing and Configuring Web Cache 10.1.2 and Oracle E-Business Suite 11i
JDeveloper
----------------------------------------------------------------------------------------------------
note 330236.1 Configuring JDeveloper For Use With Oracle Applications 11i and R12
note 357218.1 Troubleshooting JDeveloper setup for Oracle Applications
note 787209.1 How to find the correct version of JDeveloper to use with eBusiness Suite 11i or Release 12
Performance
----------------------------------------------------------------------------------------------------
note 163208.1 bde_last_analyzed.sql - Verifies CBO Statistics
note 174605.1 bde_chk_cbo.sql - Reports Database Initialization Parameters related to an Apps 12 or 11i instance
note 396009.1 Database Initialization Parameters for Oracle Applications Release 12
note 216205.1 Database Initialization Parameters for Oracle Applications 11i
note 744143.1 Tuning performance on eBusiness suite
note 169935.1 Troubleshooting Oracle Applications Performance Issues
note 244040.1 Oracle E-Business Suite Recommended Performance Patches
Security
----------------------------------------------------------------------------------------------------
note 738923.1 Oracle E-Business Suite Releases 11i and 12 Critical Patch Update note (January 2009)
note 403537.1 Best Practices for Securing Oracle E-Business Suite Release 12
note 189367.1 Best Practices for Securing the E-Business Suite Release 11i
Ihelp
----------------------------------------------------------------------------------------------------
Note 740834.1 R12: Troubleshooting iHelp
Advanced Configurations
----------------------------------------------------------------------------------------------------
note 380483.1 Oracle E-Business Suite Release 12 Additional Configuration and Deployment Options
note 384248.1 Sharing The Application Tier File System in Oracle E-Business Suite Release 12
note 217368.1 Advanced Configurations and Topologies for Enterprise Deployments of E-Business Suite 11i
note 233428.1 Sharing the Application Tier File System in Oracle Applications 11i
note 233436.1 Installing Oracle Application Server 10g with Oracle E-Business Suite Release 11i
note 364439.1 Tips and Queries for Troubleshooting Advanced Topologies
DMZ
----------------------------------------------------------------------------------------------------
note 380490.1 Oracle E-Business Suite R12 Configuration in a DMZ
note 726953.1 Case History: Implementing a Reverse Proxy Alone in the DMZ Configuration - R12
note 287176.1 DMZ Configuration with Oracle E-Business Suite 11i
note 438744.1 Case History: Implementing a Reverse Proxy Alone in a DMZ Configuration - 11i
note 460564.1 Hints and Tips for Troubleshooting the URL Firewal
Loadbalancer
----------------------------------------------------------------------------------------------------
note 380489.1 Using Load-Balancers with Oracle E-Business Suite Release 12
note 727171.1 Implementing Load Balancing On Oracle E-Business Suite - Documentation For Specific Load Balancer Hardware
note 601694.1 How To Check Session Persistence On BigIP F5 And Cisco Ace Load Balancer Appliances
note 603325.1 Using Cisco ACE Series Application Control Engine with Oracle E-Business Suite Release 12
SSL
----------------------------------------------------------------------------------------------------
note 376700.1 Using SSL with Oracle E-Business Suite Release 12
note 123718.1 11i A Guide to Understanding and Implementing SSL for Oracle Applications
Portal
----------------------------------------------------------------------------------------------------
note 305918.1 Using Oracle Portal 10g with Oracle E-Business Suite Release 11i
SSO/OID
----------------------------------------------------------------------------------------------------
note 376811.1 Integrating Oracle E-Business Suite Release 12 with 10g AS Oracle Internet Directory and Oracle Single Sign-On
note 261914.1 Integrating Oracle E-Business Suite Release 11i with Oracle Internet Directory and Oracle Single Sign-On
note 444573.1 Basic checks for user integration when using Oracle E-Business Suite 11i with Oracle AS 10g
Orace Access Manager / AccessGate
----------------------------------------------------------------------------------------------------
note 975182.1 Integrating Oracle E-Business Suite with Oracle Access Manager using Oracle E-Business Suite AccessGate
note 1077460.1 Troubleshooting Oracle Access Manager and Oracle E-Business Suite AccessGate
Webcenter
----------------------------------------------------------------------------------------------------
note 557221.1 Oracle WebCenter 10g Application Creation and Deployment Guide for Oracle E-Business Suite Release 12
Secure Enterprise Search
----------------------------------------------------------------------------------------------------
note.566097.1 Oracle E-Business Suite Secure Enterprise Search Release Notes, Release 12.1.1
note.744820.1 Oracle E-Business Suite Secure Enterprise Search Best Practices, Release 12
note.462377.1 Installing Oracle E-Business Suite Secure Enterprise Search, Release 12
note.740499.1 Oracle E-Business Suite Secure Enterprise Search Release Notes, Release 12.0.6
note 726239.1 Oracle E-Business Suite Secure Enterprise Search Troubleshooting Guidelines, Release 12
SOA/BPEL/Webservices
----------------------------------------------------------------------------------------------------
note 556540.1 Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.1
note 565922.1 Oracle E-Business Suite Integrated SOA Gateway Release Notes, Release 12.1.1
note 815196.1 Oracle E-Business Suite Integrated SOA Gateway 12.1.1 Consolidated One-Off
note 726414.1 Oracle E-Business Suite Integrated SOA Gateway Troubleshooting Guide, Release 12
note 755067.1 Using Oracle BPEL 10g with E-Business Suite Release 12.1.1
note 755069.1 EBS R12 Packager and Adapters for External Application Servers
Note 782455.1 How Can I Expose E-Business Suite Integration Interfaces as Web Services in Release 11i and R12.0
MWA
----------------------------------------------------------------------------------------------------
note 782162.1 MWA Troubleshooting Tips for Release 12
note 269991.1 MWA Troubleshooting Tips for Release 11i
Certified/Supported
----------------------------------------------------------------------------------------------------
http://blogs.oracle.com/stevenchan/certifications.html
note 363827.1 Rebaselined Oracle Applications Technology Components for Releases 11.5.7, 11.5.8, 11.5.9, and 11.5.10
note 883202.1 Minimum Baseline Patch Requirements for Extended Support on Oracle E-Business Suite 11.5.10
WEBADI
----------------------------------------------------------------------------------------------------
note 417692.1 Installing, Configuring and Troubleshooting Web ADI (Web Applications Desktop Integrator)
note 452452.1 R12 Installing, Configuring and Troubleshooting Web ADI (Web Applications Desktop Integrator)
note 294739.1 How to enable tracing for WEBADI
note 726989.1 List of Patches in Web Applications Desktop Integrator (Web ADI) for Releases 11i and 12
Diagnostics
----------------------------------------------------------------------------------------------------
note 167000.1 E-Business Suite Diagnostics Installation Guide
note 421245.1 E-Business Suite Diagnostics References for R12
note 179661.1 E-Business Suite Diagnostics 11i Test Catalog
Installation
----------------------------------------------------------------------------------------------------
note 761564.1 Oracle Applications Installation and Upgrade Notes Release 12 (12.1.1) for Linux x86
note 402310.1 Oracle Applications Installation and Upgrade notes Release 12 (12.0) for Linux (32-bit)
note 406982.1 Cloning Oracle Applications Release 12 with Rapid Clone
note 559518.1 Cloning Oracle E-Business Suite Release 12 RAC-Enabled Systems with Rapid Clone
note 421409.1 Unbreakable Linux enviroment check before R12 install
note 458533.1 How to Enable Enterprise Manager on the Oracle E-Business Suite Release 12
note 603716.1 Using AS10g AS Control with eBusiness Suite Rel 12
note 452120.1 How to locate the log files and troubleshoot RapidWiz for R12
note 316806.1 Oracle Applications Installation Update notes, Release 11i (11.5.10.2)
note:230672.1 Cloning Oracle Applications Release 11i with Rapid Clone
note 207296.1 How to Find out Linux Version Information?
Database
----------------------------------------------------------------------------------------------------
note:454750.1 Oracle Apps Release 12 with Oracle Database 10.2.0 interoperability notes
note 735276.1 Interoperability notes E-Business Suite R12 with Oracle Database 11gR1
note 388577.1 Configuring Oracle Applications Release 12 with 10g R2 RAC
note 466649.1 Using Oracle 11g Release 1 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12
note 216550.1 Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0)
note 362203.1 Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0)
note 452783.1 Oracle Applications Release 11i with Oracle 11g Release 1 (11.1.0)
note 362135.1 Configuring Oracle Applications Release 11i with 10g R2 RAC and ASM
note 554539.1 Using Database Partitioning with Oracle E-Business Suite
Installation and Diagnostics notes available related to the Oracle E-Business Suite Technology stack
Applies to:
Oracle Applications Technology Stack - Version: 11.5.10.2 to 12.0.6
Information in this document applies to any platform.
Goal
This note is to list the main Setup, Installation and Diagnostics notes available related to the Oracle E-Business Suite Technology stack.
Solution
Java
----------------------------------------------------------------------------------------------------
note 418664.1 Overview of Using Java with Oracle E-Business Suite Release 12
note 455492.1 Using Latest Update of Java 6.0 with Oracle E-Business Suite Release 12
note 384249.1 Using Latest Update of JDK 5.0 with Oracle E-Business Suite Release 12
note 300482.1 Overview of Using Java with Oracle E-Business Suite Release 11i
note 401561.1 Using J2SE Version 6 with Oracle E-Business Suite 11i
note 304099.1 Using J2SE Version 5.0 with Oracle E-Business Suite 11i, Release 11.5.10
note 246105.1 Upgrading to J2SE 1.4.2 with Oracle Applications 11i
note 130091.1 Upgrading Oracle Applications 11i to use JDK 1.3
JRE/Jinitiator
----------------------------------------------------------------------------------------------------
note 389422.1 Recommended Browsers for Oracle E-Business Suite Release 12
note 393931.1 Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12
note 285218.1 Recommended Browsers for Oracle Applications 11i
note 290807.1 Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i
note 124606.1 Upgrading JInitiator with Oracle E-Business Suite 11i
Forms
----------------------------------------------------------------------------------------------------
note 437878.1 Upgrading OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12
note 750359.1 Upgrading to Previous Version of OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12
note 384241.1 Using Forms Socket Mode with Oracle E-Business Suite Release 12
note 438652.1 R12 Forms Runtime Diagnostics (FRD), Tracing And Logging For Forms In Oracle Applications
note 125767.1 Upgrading Developer 6i with Oracle Applications 11i
note 232313.1 Information on Previous Versions of Developer 6i Patchsets
note 201340.1 Using Forms Listener Servlet with Oracle Applications 11i
note 150168.1 Obtaining Forms Runtime Diagnostics (FRD) In Oracle Applications 11i
note 760250.1 Diagnosing Forms Mouse Focus Problems Using JRE in Release 11i
OracleAS
----------------------------------------------------------------------------------------------------
note 454811.1 Upgrading to the Latest OracleAS 10g 10.1.3.x Patch Set in Oracle E-Business Suite Release 12
note 743518.1 Starting up AS10g services in an EBusiness Suite Release 12 environment
JDBC
----------------------------------------------------------------------------------------------------
note 557194.1 monitor_jdbc_conn.sql - Script to monitor JDBC connections in Apps eBusiness Suite
JVM
----------------------------------------------------------------------------------------------------
note 362851.1 Guidelines to setup the JVM in Apps Ebusiness Suite 11i and R12
note 567551.1 Configuring various JVM tuning parameters for Oracle E-Business suite 11i and R12
note 370583.1 Basic troubleshooting of JVM consuming cpu or too many JDBC connections in Apps 11i
Apache/mod_jserv
----------------------------------------------------------------------------------------------------
note 230688.1 11i Basic Apache/mod_jserv Troubleshooting with Hello.class
Debug/Trace
----------------------------------------------------------------------------------------------------
note 422419.1 R12 - How To Enable and Collect Debug for HTTP, OC4J and OPMN
Note 443671.1 R12 - Collecting Configuration Information for HTTP, OC4J and OPMN
note 427848.1 How to Enable Execution Context ID (ECID) in the R12 access_log
note 455154.1 R12: How To Obtain A Thread Dump When OC4J is shutdown
note 603390.1 How To Create a User Event Trace in R11i / R12
OA Framework
----------------------------------------------------------------------------------------------------
note 391554.1 Oracle Application Framework Documentation Resources, Release 12
note 275880.1 Oracle Application Framework Release 11i Documentation Road Map
note 275875.1 Oracle Application Framework Troubleshooting Release 11i (11.5.10)
note 357597.1 How To Generate A SQL Trace In OA Framework For Oracle Applications
WebCache
----------------------------------------------------------------------------------------------------
note 380486.1 Installing and Configuring Web Cache 10g and Oracle E-Business Suite 12
note 306653.1 Installing and Configuring Web Cache 10.1.2 and Oracle E-Business Suite 11i
JDeveloper
----------------------------------------------------------------------------------------------------
note 330236.1 Configuring JDeveloper For Use With Oracle Applications 11i and R12
note 357218.1 Troubleshooting JDeveloper setup for Oracle Applications
note 787209.1 How to find the correct version of JDeveloper to use with eBusiness Suite 11i or Release 12
Performance
----------------------------------------------------------------------------------------------------
note 163208.1 bde_last_analyzed.sql - Verifies CBO Statistics
note 174605.1 bde_chk_cbo.sql - Reports Database Initialization Parameters related to an Apps 12 or 11i instance
note 396009.1 Database Initialization Parameters for Oracle Applications Release 12
note 216205.1 Database Initialization Parameters for Oracle Applications 11i
note 744143.1 Tuning performance on eBusiness suite
note 169935.1 Troubleshooting Oracle Applications Performance Issues
note 244040.1 Oracle E-Business Suite Recommended Performance Patches
Security
----------------------------------------------------------------------------------------------------
note 738923.1 Oracle E-Business Suite Releases 11i and 12 Critical Patch Update note (January 2009)
note 403537.1 Best Practices for Securing Oracle E-Business Suite Release 12
note 189367.1 Best Practices for Securing the E-Business Suite Release 11i
Ihelp
----------------------------------------------------------------------------------------------------
Note 740834.1 R12: Troubleshooting iHelp
Advanced Configurations
----------------------------------------------------------------------------------------------------
note 380483.1 Oracle E-Business Suite Release 12 Additional Configuration and Deployment Options
note 384248.1 Sharing The Application Tier File System in Oracle E-Business Suite Release 12
note 217368.1 Advanced Configurations and Topologies for Enterprise Deployments of E-Business Suite 11i
note 233428.1 Sharing the Application Tier File System in Oracle Applications 11i
note 233436.1 Installing Oracle Application Server 10g with Oracle E-Business Suite Release 11i
note 364439.1 Tips and Queries for Troubleshooting Advanced Topologies
DMZ
----------------------------------------------------------------------------------------------------
note 380490.1 Oracle E-Business Suite R12 Configuration in a DMZ
note 726953.1 Case History: Implementing a Reverse Proxy Alone in the DMZ Configuration - R12
note 287176.1 DMZ Configuration with Oracle E-Business Suite 11i
note 438744.1 Case History: Implementing a Reverse Proxy Alone in a DMZ Configuration - 11i
note 460564.1 Hints and Tips for Troubleshooting the URL Firewal
Loadbalancer
----------------------------------------------------------------------------------------------------
note 380489.1 Using Load-Balancers with Oracle E-Business Suite Release 12
note 727171.1 Implementing Load Balancing On Oracle E-Business Suite - Documentation For Specific Load Balancer Hardware
note 601694.1 How To Check Session Persistence On BigIP F5 And Cisco Ace Load Balancer Appliances
note 603325.1 Using Cisco ACE Series Application Control Engine with Oracle E-Business Suite Release 12
SSL
----------------------------------------------------------------------------------------------------
note 376700.1 Using SSL with Oracle E-Business Suite Release 12
note 123718.1 11i A Guide to Understanding and Implementing SSL for Oracle Applications
Portal
----------------------------------------------------------------------------------------------------
note 305918.1 Using Oracle Portal 10g with Oracle E-Business Suite Release 11i
SSO/OID
----------------------------------------------------------------------------------------------------
note 376811.1 Integrating Oracle E-Business Suite Release 12 with 10g AS Oracle Internet Directory and Oracle Single Sign-On
note 261914.1 Integrating Oracle E-Business Suite Release 11i with Oracle Internet Directory and Oracle Single Sign-On
note 444573.1 Basic checks for user integration when using Oracle E-Business Suite 11i with Oracle AS 10g
Orace Access Manager / AccessGate
----------------------------------------------------------------------------------------------------
note 975182.1 Integrating Oracle E-Business Suite with Oracle Access Manager using Oracle E-Business Suite AccessGate
note 1077460.1 Troubleshooting Oracle Access Manager and Oracle E-Business Suite AccessGate
Webcenter
----------------------------------------------------------------------------------------------------
note 557221.1 Oracle WebCenter 10g Application Creation and Deployment Guide for Oracle E-Business Suite Release 12
Secure Enterprise Search
----------------------------------------------------------------------------------------------------
note.566097.1 Oracle E-Business Suite Secure Enterprise Search Release Notes, Release 12.1.1
note.744820.1 Oracle E-Business Suite Secure Enterprise Search Best Practices, Release 12
note.462377.1 Installing Oracle E-Business Suite Secure Enterprise Search, Release 12
note.740499.1 Oracle E-Business Suite Secure Enterprise Search Release Notes, Release 12.0.6
note 726239.1 Oracle E-Business Suite Secure Enterprise Search Troubleshooting Guidelines, Release 12
SOA/BPEL/Webservices
----------------------------------------------------------------------------------------------------
note 556540.1 Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.1
note 565922.1 Oracle E-Business Suite Integrated SOA Gateway Release Notes, Release 12.1.1
note 815196.1 Oracle E-Business Suite Integrated SOA Gateway 12.1.1 Consolidated One-Off
note 726414.1 Oracle E-Business Suite Integrated SOA Gateway Troubleshooting Guide, Release 12
note 755067.1 Using Oracle BPEL 10g with E-Business Suite Release 12.1.1
note 755069.1 EBS R12 Packager and Adapters for External Application Servers
Note 782455.1 How Can I Expose E-Business Suite Integration Interfaces as Web Services in Release 11i and R12.0
MWA
----------------------------------------------------------------------------------------------------
note 782162.1 MWA Troubleshooting Tips for Release 12
note 269991.1 MWA Troubleshooting Tips for Release 11i
Certified/Supported
----------------------------------------------------------------------------------------------------
http://blogs.oracle.com/stevenchan/certifications.html
note 363827.1 Rebaselined Oracle Applications Technology Components for Releases 11.5.7, 11.5.8, 11.5.9, and 11.5.10
note 883202.1 Minimum Baseline Patch Requirements for Extended Support on Oracle E-Business Suite 11.5.10
WEBADI
----------------------------------------------------------------------------------------------------
note 417692.1 Installing, Configuring and Troubleshooting Web ADI (Web Applications Desktop Integrator)
note 452452.1 R12 Installing, Configuring and Troubleshooting Web ADI (Web Applications Desktop Integrator)
note 294739.1 How to enable tracing for WEBADI
note 726989.1 List of Patches in Web Applications Desktop Integrator (Web ADI) for Releases 11i and 12
Diagnostics
----------------------------------------------------------------------------------------------------
note 167000.1 E-Business Suite Diagnostics Installation Guide
note 421245.1 E-Business Suite Diagnostics References for R12
note 179661.1 E-Business Suite Diagnostics 11i Test Catalog
Installation
----------------------------------------------------------------------------------------------------
note 761564.1 Oracle Applications Installation and Upgrade Notes Release 12 (12.1.1) for Linux x86
note 402310.1 Oracle Applications Installation and Upgrade notes Release 12 (12.0) for Linux (32-bit)
note 406982.1 Cloning Oracle Applications Release 12 with Rapid Clone
note 559518.1 Cloning Oracle E-Business Suite Release 12 RAC-Enabled Systems with Rapid Clone
note 421409.1 Unbreakable Linux enviroment check before R12 install
note 458533.1 How to Enable Enterprise Manager on the Oracle E-Business Suite Release 12
note 603716.1 Using AS10g AS Control with eBusiness Suite Rel 12
note 452120.1 How to locate the log files and troubleshoot RapidWiz for R12
note 316806.1 Oracle Applications Installation Update notes, Release 11i (11.5.10.2)
note:230672.1 Cloning Oracle Applications Release 11i with Rapid Clone
note 207296.1 How to Find out Linux Version Information?
Database
----------------------------------------------------------------------------------------------------
note:454750.1 Oracle Apps Release 12 with Oracle Database 10.2.0 interoperability notes
note 735276.1 Interoperability notes E-Business Suite R12 with Oracle Database 11gR1
note 388577.1 Configuring Oracle Applications Release 12 with 10g R2 RAC
note 466649.1 Using Oracle 11g Release 1 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12
note 216550.1 Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0)
note 362203.1 Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0)
note 452783.1 Oracle Applications Release 11i with Oracle 11g Release 1 (11.1.0)
note 362135.1 Configuring Oracle Applications Release 11i with 10g R2 RAC and ASM
note 554539.1 Using Database Partitioning with Oracle E-Business Suite
Oracle Applications Technology Stack - Version: 11.5.10.2 to 12.0.6
Information in this document applies to any platform.
Goal
This note is to list the main Setup, Installation and Diagnostics notes available related to the Oracle E-Business Suite Technology stack.
Solution
Java
----------------------------------------------------------------------------------------------------
note 418664.1 Overview of Using Java with Oracle E-Business Suite Release 12
note 455492.1 Using Latest Update of Java 6.0 with Oracle E-Business Suite Release 12
note 384249.1 Using Latest Update of JDK 5.0 with Oracle E-Business Suite Release 12
note 300482.1 Overview of Using Java with Oracle E-Business Suite Release 11i
note 401561.1 Using J2SE Version 6 with Oracle E-Business Suite 11i
note 304099.1 Using J2SE Version 5.0 with Oracle E-Business Suite 11i, Release 11.5.10
note 246105.1 Upgrading to J2SE 1.4.2 with Oracle Applications 11i
note 130091.1 Upgrading Oracle Applications 11i to use JDK 1.3
JRE/Jinitiator
----------------------------------------------------------------------------------------------------
note 389422.1 Recommended Browsers for Oracle E-Business Suite Release 12
note 393931.1 Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12
note 285218.1 Recommended Browsers for Oracle Applications 11i
note 290807.1 Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i
note 124606.1 Upgrading JInitiator with Oracle E-Business Suite 11i
Forms
----------------------------------------------------------------------------------------------------
note 437878.1 Upgrading OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12
note 750359.1 Upgrading to Previous Version of OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12
note 384241.1 Using Forms Socket Mode with Oracle E-Business Suite Release 12
note 438652.1 R12 Forms Runtime Diagnostics (FRD), Tracing And Logging For Forms In Oracle Applications
note 125767.1 Upgrading Developer 6i with Oracle Applications 11i
note 232313.1 Information on Previous Versions of Developer 6i Patchsets
note 201340.1 Using Forms Listener Servlet with Oracle Applications 11i
note 150168.1 Obtaining Forms Runtime Diagnostics (FRD) In Oracle Applications 11i
note 760250.1 Diagnosing Forms Mouse Focus Problems Using JRE in Release 11i
OracleAS
----------------------------------------------------------------------------------------------------
note 454811.1 Upgrading to the Latest OracleAS 10g 10.1.3.x Patch Set in Oracle E-Business Suite Release 12
note 743518.1 Starting up AS10g services in an EBusiness Suite Release 12 environment
JDBC
----------------------------------------------------------------------------------------------------
note 557194.1 monitor_jdbc_conn.sql - Script to monitor JDBC connections in Apps eBusiness Suite
JVM
----------------------------------------------------------------------------------------------------
note 362851.1 Guidelines to setup the JVM in Apps Ebusiness Suite 11i and R12
note 567551.1 Configuring various JVM tuning parameters for Oracle E-Business suite 11i and R12
note 370583.1 Basic troubleshooting of JVM consuming cpu or too many JDBC connections in Apps 11i
Apache/mod_jserv
----------------------------------------------------------------------------------------------------
note 230688.1 11i Basic Apache/mod_jserv Troubleshooting with Hello.class
Debug/Trace
----------------------------------------------------------------------------------------------------
note 422419.1 R12 - How To Enable and Collect Debug for HTTP, OC4J and OPMN
Note 443671.1 R12 - Collecting Configuration Information for HTTP, OC4J and OPMN
note 427848.1 How to Enable Execution Context ID (ECID) in the R12 access_log
note 455154.1 R12: How To Obtain A Thread Dump When OC4J is shutdown
note 603390.1 How To Create a User Event Trace in R11i / R12
OA Framework
----------------------------------------------------------------------------------------------------
note 391554.1 Oracle Application Framework Documentation Resources, Release 12
note 275880.1 Oracle Application Framework Release 11i Documentation Road Map
note 275875.1 Oracle Application Framework Troubleshooting Release 11i (11.5.10)
note 357597.1 How To Generate A SQL Trace In OA Framework For Oracle Applications
WebCache
----------------------------------------------------------------------------------------------------
note 380486.1 Installing and Configuring Web Cache 10g and Oracle E-Business Suite 12
note 306653.1 Installing and Configuring Web Cache 10.1.2 and Oracle E-Business Suite 11i
JDeveloper
----------------------------------------------------------------------------------------------------
note 330236.1 Configuring JDeveloper For Use With Oracle Applications 11i and R12
note 357218.1 Troubleshooting JDeveloper setup for Oracle Applications
note 787209.1 How to find the correct version of JDeveloper to use with eBusiness Suite 11i or Release 12
Performance
----------------------------------------------------------------------------------------------------
note 163208.1 bde_last_analyzed.sql - Verifies CBO Statistics
note 174605.1 bde_chk_cbo.sql - Reports Database Initialization Parameters related to an Apps 12 or 11i instance
note 396009.1 Database Initialization Parameters for Oracle Applications Release 12
note 216205.1 Database Initialization Parameters for Oracle Applications 11i
note 744143.1 Tuning performance on eBusiness suite
note 169935.1 Troubleshooting Oracle Applications Performance Issues
note 244040.1 Oracle E-Business Suite Recommended Performance Patches
Security
----------------------------------------------------------------------------------------------------
note 738923.1 Oracle E-Business Suite Releases 11i and 12 Critical Patch Update note (January 2009)
note 403537.1 Best Practices for Securing Oracle E-Business Suite Release 12
note 189367.1 Best Practices for Securing the E-Business Suite Release 11i
Ihelp
----------------------------------------------------------------------------------------------------
Note 740834.1 R12: Troubleshooting iHelp
Advanced Configurations
----------------------------------------------------------------------------------------------------
note 380483.1 Oracle E-Business Suite Release 12 Additional Configuration and Deployment Options
note 384248.1 Sharing The Application Tier File System in Oracle E-Business Suite Release 12
note 217368.1 Advanced Configurations and Topologies for Enterprise Deployments of E-Business Suite 11i
note 233428.1 Sharing the Application Tier File System in Oracle Applications 11i
note 233436.1 Installing Oracle Application Server 10g with Oracle E-Business Suite Release 11i
note 364439.1 Tips and Queries for Troubleshooting Advanced Topologies
DMZ
----------------------------------------------------------------------------------------------------
note 380490.1 Oracle E-Business Suite R12 Configuration in a DMZ
note 726953.1 Case History: Implementing a Reverse Proxy Alone in the DMZ Configuration - R12
note 287176.1 DMZ Configuration with Oracle E-Business Suite 11i
note 438744.1 Case History: Implementing a Reverse Proxy Alone in a DMZ Configuration - 11i
note 460564.1 Hints and Tips for Troubleshooting the URL Firewal
Loadbalancer
----------------------------------------------------------------------------------------------------
note 380489.1 Using Load-Balancers with Oracle E-Business Suite Release 12
note 727171.1 Implementing Load Balancing On Oracle E-Business Suite - Documentation For Specific Load Balancer Hardware
note 601694.1 How To Check Session Persistence On BigIP F5 And Cisco Ace Load Balancer Appliances
note 603325.1 Using Cisco ACE Series Application Control Engine with Oracle E-Business Suite Release 12
SSL
----------------------------------------------------------------------------------------------------
note 376700.1 Using SSL with Oracle E-Business Suite Release 12
note 123718.1 11i A Guide to Understanding and Implementing SSL for Oracle Applications
Portal
----------------------------------------------------------------------------------------------------
note 305918.1 Using Oracle Portal 10g with Oracle E-Business Suite Release 11i
SSO/OID
----------------------------------------------------------------------------------------------------
note 376811.1 Integrating Oracle E-Business Suite Release 12 with 10g AS Oracle Internet Directory and Oracle Single Sign-On
note 261914.1 Integrating Oracle E-Business Suite Release 11i with Oracle Internet Directory and Oracle Single Sign-On
note 444573.1 Basic checks for user integration when using Oracle E-Business Suite 11i with Oracle AS 10g
Orace Access Manager / AccessGate
----------------------------------------------------------------------------------------------------
note 975182.1 Integrating Oracle E-Business Suite with Oracle Access Manager using Oracle E-Business Suite AccessGate
note 1077460.1 Troubleshooting Oracle Access Manager and Oracle E-Business Suite AccessGate
Webcenter
----------------------------------------------------------------------------------------------------
note 557221.1 Oracle WebCenter 10g Application Creation and Deployment Guide for Oracle E-Business Suite Release 12
Secure Enterprise Search
----------------------------------------------------------------------------------------------------
note.566097.1 Oracle E-Business Suite Secure Enterprise Search Release Notes, Release 12.1.1
note.744820.1 Oracle E-Business Suite Secure Enterprise Search Best Practices, Release 12
note.462377.1 Installing Oracle E-Business Suite Secure Enterprise Search, Release 12
note.740499.1 Oracle E-Business Suite Secure Enterprise Search Release Notes, Release 12.0.6
note 726239.1 Oracle E-Business Suite Secure Enterprise Search Troubleshooting Guidelines, Release 12
SOA/BPEL/Webservices
----------------------------------------------------------------------------------------------------
note 556540.1 Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.1
note 565922.1 Oracle E-Business Suite Integrated SOA Gateway Release Notes, Release 12.1.1
note 815196.1 Oracle E-Business Suite Integrated SOA Gateway 12.1.1 Consolidated One-Off
note 726414.1 Oracle E-Business Suite Integrated SOA Gateway Troubleshooting Guide, Release 12
note 755067.1 Using Oracle BPEL 10g with E-Business Suite Release 12.1.1
note 755069.1 EBS R12 Packager and Adapters for External Application Servers
Note 782455.1 How Can I Expose E-Business Suite Integration Interfaces as Web Services in Release 11i and R12.0
MWA
----------------------------------------------------------------------------------------------------
note 782162.1 MWA Troubleshooting Tips for Release 12
note 269991.1 MWA Troubleshooting Tips for Release 11i
Certified/Supported
----------------------------------------------------------------------------------------------------
http://blogs.oracle.com/stevenchan/certifications.html
note 363827.1 Rebaselined Oracle Applications Technology Components for Releases 11.5.7, 11.5.8, 11.5.9, and 11.5.10
note 883202.1 Minimum Baseline Patch Requirements for Extended Support on Oracle E-Business Suite 11.5.10
WEBADI
----------------------------------------------------------------------------------------------------
note 417692.1 Installing, Configuring and Troubleshooting Web ADI (Web Applications Desktop Integrator)
note 452452.1 R12 Installing, Configuring and Troubleshooting Web ADI (Web Applications Desktop Integrator)
note 294739.1 How to enable tracing for WEBADI
note 726989.1 List of Patches in Web Applications Desktop Integrator (Web ADI) for Releases 11i and 12
Diagnostics
----------------------------------------------------------------------------------------------------
note 167000.1 E-Business Suite Diagnostics Installation Guide
note 421245.1 E-Business Suite Diagnostics References for R12
note 179661.1 E-Business Suite Diagnostics 11i Test Catalog
Installation
----------------------------------------------------------------------------------------------------
note 761564.1 Oracle Applications Installation and Upgrade Notes Release 12 (12.1.1) for Linux x86
note 402310.1 Oracle Applications Installation and Upgrade notes Release 12 (12.0) for Linux (32-bit)
note 406982.1 Cloning Oracle Applications Release 12 with Rapid Clone
note 559518.1 Cloning Oracle E-Business Suite Release 12 RAC-Enabled Systems with Rapid Clone
note 421409.1 Unbreakable Linux enviroment check before R12 install
note 458533.1 How to Enable Enterprise Manager on the Oracle E-Business Suite Release 12
note 603716.1 Using AS10g AS Control with eBusiness Suite Rel 12
note 452120.1 How to locate the log files and troubleshoot RapidWiz for R12
note 316806.1 Oracle Applications Installation Update notes, Release 11i (11.5.10.2)
note:230672.1 Cloning Oracle Applications Release 11i with Rapid Clone
note 207296.1 How to Find out Linux Version Information?
Database
----------------------------------------------------------------------------------------------------
note:454750.1 Oracle Apps Release 12 with Oracle Database 10.2.0 interoperability notes
note 735276.1 Interoperability notes E-Business Suite R12 with Oracle Database 11gR1
note 388577.1 Configuring Oracle Applications Release 12 with 10g R2 RAC
note 466649.1 Using Oracle 11g Release 1 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12
note 216550.1 Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0)
note 362203.1 Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0)
note 452783.1 Oracle Applications Release 11i with Oracle 11g Release 1 (11.1.0)
note 362135.1 Configuring Oracle Applications Release 11i with 10g R2 RAC and ASM
note 554539.1 Using Database Partitioning with Oracle E-Business Suite
Wednesday, May 5, 2010
How to find location of Install, Autoconfig, Patching , Clone and other logs in R12
How to find location of Install, Autoconfig, Patching , Clone and other logs in R12 [ID 804603.1]
--------------------------------------------------------------------------------
Modified 15-JUL-2009 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
--------------------------------------------------------------------------------
Applies to:
Oracle Applications Manager - Version: 12.0
Information in this document applies to any platform.
Goal
How to find location of Install, Autoconfig, Patching , Clone and other logs in R12
Solution
Log files are useful in troubleshooting issues in Oracle Applications.
Here is the list of Log file location in Oracle Applications for Startup/Shutdown, Cloning, Patching, DB & Apps Listener and various components in Apps R12/12i:
Note:Instance top ($INST_TOP) is new directory added in R12 to keep the log files ,Startup/stop scripts for the application tier
A. Startup/Shutdown Log files for Application Tier in R12
=========================================================
i) Startup/Shutdown error message text files like adapcctl.txt, adcmctl.txt… :
$INST_TOP/apps/$CONTEXT_NAME/logs/appl/admin/log
ii) Startup/Shutdown error message related to tech stack (10.1.2, 10.1.3 forms/reports/web) :
$INST_TOP/apps/$CONTEXT_NAME/logs/ora/ (10.1.2 & 10.1.3)
$INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1.3/Apache/error_log[timestamp]
$INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1.3/opmn/ (OC4J~…, oa*, opmn.log)
$INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1.2/network/ (listener log)
$INST_TOP/apps/$CONTEXT_NAME/logs/appl/conc/log (CM log files)
B. Log files related to cloning in R12
=======================================
Preclone (adpreclone.pl) log files in source instance
i) Database Tier-$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/(StageDBTier_
--------------------------------------------------------------------------------
Modified 15-JUL-2009 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
--------------------------------------------------------------------------------
Applies to:
Oracle Applications Manager - Version: 12.0
Information in this document applies to any platform.
Goal
How to find location of Install, Autoconfig, Patching , Clone and other logs in R12
Solution
Log files are useful in troubleshooting issues in Oracle Applications.
Here is the list of Log file location in Oracle Applications for Startup/Shutdown, Cloning, Patching, DB & Apps Listener and various components in Apps R12/12i:
Note:Instance top ($INST_TOP) is new directory added in R12 to keep the log files ,Startup/stop scripts for the application tier
A. Startup/Shutdown Log files for Application Tier in R12
=========================================================
i) Startup/Shutdown error message text files like adapcctl.txt, adcmctl.txt… :
$INST_TOP/apps/$CONTEXT_NAME/logs/appl/admin/log
ii) Startup/Shutdown error message related to tech stack (10.1.2, 10.1.3 forms/reports/web) :
$INST_TOP/apps/$CONTEXT_NAME/logs/ora/ (10.1.2 & 10.1.3)
$INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1.3/Apache/error_log[timestamp]
$INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1.3/opmn/ (OC4J~…, oa*, opmn.log)
$INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1.2/network/ (listener log)
$INST_TOP/apps/$CONTEXT_NAME/logs/appl/conc/log (CM log files)
B. Log files related to cloning in R12
=======================================
Preclone (adpreclone.pl) log files in source instance
i) Database Tier-$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/(StageDBTier_
Tuesday, May 4, 2010
How to mount the HDD in Linux
Configuration
A single partition would be, edit /etc/fstab
/dev/sda1 /mnt/usbhd1 auto defaults 0 0
Having created the entry in /etc/fstab, you need to create matching mount point in the actual filesystem.
# mkdir /mnt/usbhd1
You should now be able to mount your USB HDD with a command like
# mount /mnt/usbhd1
A single partition would be, edit /etc/fstab
/dev/sda1 /mnt/usbhd1 auto defaults 0 0
Having created the entry in /etc/fstab, you need to create matching mount point in the actual filesystem.
# mkdir /mnt/usbhd1
You should now be able to mount your USB HDD with a command like
# mount /mnt/usbhd1
Oracle Time Zone
Oracle Time Zone
Just when you thought you knew where you were, Oracle has implemented time zones to totally zone us out. Come along and let's figure where we are on this great planet.
A few articles back I wrote on a comparison between the DATE datatype and the TIMESTAMP datatype. This article goes one step further and explores Oracle's TIME ZONE feature of the TIMESTAMP datatype. In particular, Oracle has added the "WITH TIME ZONE" and the "WITH LOCAL TIME ZONE" to the TIMESTAMP datatype.
Valid Time Zones
You have two options when setting which time zone the database belongs to. You can either qualify it as a displacement from GMT/UTC in the format of 'hh:mm' or you can specify it as a name that has an entry in the V$TIMEZONE table. Listing 1 shows the SQL I used to display the valid time zone name in the Mountain Standard Time Zone.
Listing 1
Show valid time zone names for MST
SQL> select tzname,tzabbrev
from V$TIMEZONE_NAMES
where tzabbrev = 'MST'
TZNAME TZABBREV
------------------------- ----------
America/Denver MST
America/Edmonton MST
America/Ensenada MST
America/Mazatlan MST
America/Mexico_City MST
America/Phoenix MST
America/Regina MST
America/Shiprock MST
America/Tijuana MST
Canada/East-Saskatchewan MST
Canada/Mountain MST
Canada/Saskatchewan MST
Europe/Moscow MST
Mexico/BajaNorte MST
Mexico/BajaSur MST
Mexico/General MST
MST MST
MST7MDT MST
Navajo MST
US/Arizona MST
US/Mountain MST
W-SU MST
DBTIMEZONE
At the core of time zones is the database time zone. You can look at the time zone that was selected at database creation by issuing the SQL in Listing 2. If you want to change the DBTIMEZONE you will need to issue an ALTER DATBASE command such as in Listing 3. In order for the new DBTIMEZONE to take effect, you must bounce the database. In addition, if you have any data type columns that are of the TIMESTAMP with TIME ZONE defined, you will not be able to reset the DBTIMEZONE. After bouncing the database, you can issue the SQL in Listing 4 to validate that the change has taken place. If you wanted to switch back to the "hh:mm" format for DBTIMEZONE, just issue the SQL in Listing 5.
Listing 2
Check the database time zone
SQL> select DBTIMEZONE from dual;
DBTIME
------
-07:00
Listing 3
Changing the database time zone
SQL> ALTER database SET TIME_ZONE = 'America/Denver';
Database altered.
Listing 4
Validate the change in DBTIMEZONE
SQL> select DBTIMEZONE from dual;
DBTIMEZONE
---------------
America/Denver
Listing 5
Switch back DBTIMEZONE to hh:mm format
SQL> ALTER database SET TIME_ZONE = '-07:00';
SESSIONTIMEZONE
If you do not want to use the database time zone, Oracle gives you the option to set the time zone at the session level. Issue the SQL in Listing 6 if you want a different time zone for the current session to which you are connected. You can check the session time zone by issuing the SQL in Listing 7.
Listing 6
Set time zone at the session level
SQL> alter session set TIME_ZONE='-03:00';
Session altered.
Listing 7
Check session level time zone
SQL> select SESSIONTIMEZONE from dual;
SESSIONTIMEZONE
-------------------------------------------------
-03:00
SYSTIMESTAMP
Just as there is a call to SYSDATE to get the current system date and time, there is a call to get the current system date, time and time zone. The data type returned is of TIMESTAMP WITH TIME ZONE. Issue the SQL in Listing 8 to get the current system time information.
Listing 8
Get current system timestamp with time zone information
SQL> select SYSTIMESTAMP from dual;
SYSTIMESTAMP
-----------------------------------------------
01-SEP-03 10.53.13.574000 AM -07:00
CURRENT_TIMESTAMP
The counter part of the SYSTIMESTAMP function for session current date and time is the CURRENT_TIMESTAMP function call. This will return what the current time stamp of the session is in relation to the session time zone (SESSIONTIMEZONE). Therefore, if we have the session time zone as defined in Listing 6, we can check the timestamp of the session by issuing the SQL in Listing 9.
Listing 9
Local timestamp for session
SQL> select CURRENT_TIMESTAMP from dual;
CURRENT_TIMESTAMP
-------------------------------------------------
01-SEP-03 02.53.33.753000 PM –03:00
TIMESTAMP datatype with TIME ZONE Information
At the heart of storing time zone information within a table, Oracle has defined the TIMESTAMP data type. This is Oracle's great new hope for giving the old DATE datatype a more granular mechanism of holding not only date and time information but also fractional seconds. Look at A Comparison of Oracle's DATE and TIMESTAMP Datatypes for a discussion of this databtype. For the remainder of this article and for the purposes of exploiting the time zone options for the TIMESTAMP datatype, I have created a table as defined in Table 1. In Listing 10, I have created a quick example of how the TIMESTAMP WITH TIME ZONE and TIMESTAMP WITH LOCAL TIME ZONE datatypes will behave when used to store information. To begin with I have set the DBTIMEZONE and SESSION TIMEZONE to be the same value '-07:00'. I then insert into the DATE_TABLE the value of a system time stamp. I then change the time zone for the current session only to be '-03:00'. This will set the current session four hours ahead of the database time zone. I then insert into the DATE_TABLE a row that will hold the current session timestamp. The main idea to grasp here is that the column with datatype TIMESTAMP WITH TIME ZONE stores and displays the explicit time supplied from the INSERT statement. The column with datatype TIMESTAMP WITH LOCAL TIME ZONE stores the explicit time supplied but will display a value that is relative to the current session time zone. This means that if you want hard and fast TIMESTAMPS with time zone information stored, you should use the TIMESTAMP WITH TIME ZONE datatype. If you are concerned more with giving date and time information to customers in different time zones and represented in their local time, you should use the TIMESTAMP WITH LOCAL TIME ZONE datatype.
Table 1:
Create table with different TIMESTAMP columns
create table date_table (
time_stamp_tz TIMESTAMP WITH TIME ZONE,
time_stamp_ltz TIMESTAMP WITH LOCAL TIME ZONE);
LISTING 10
Inserting SYSTIMESTAMP into DATE_TABLE
SQL> select dbtimezone,sessiontimezone from dual;
DBTIMEZONE SESSIONTIMEZONE
---------- ----------------
-07:00 -07:00
SQL> insert into date_table values (SYSTIMESTAMP,SYSTIMESTAMP);
1 row created.
SQL> alter session set time_zone='-03:00';
Session altered.
SQL> select dbtimezone,sessiontimezone from dual;
DBTIMEZONE SESSIONTIMEZONE
---------- ----------------
-07:00 -03:00
SQL> insert into date_table values (LOCALTIMESTAMP,LOCALTIMESTAMP );
1 row created.
SQL> select time_stamp_tz, time_stamp_ltz from date_table;
TIME_STAMP_TZ TIME_STAMP_LTZ
------------------------------------- ------------------------------
01-SEP-03 10.57.36.642000 AM -07:00 01-SEP-03 02.57.36.642000 PM
01-SEP-03 02.57.48.549000 PM -03:00 01-SEP-03 02.57.48.549000 PM
SQL> alter session set time_zone='-07:00';
Session altered.
SQL> select time_stamp_tz, time_stamp_ltz from date_table;
TIME_STAMP_TZ TIME_STAMP_LTZ
------------------------------------- ------------------------------
01-SEP-03 10.57.36.642000 AM -07:00 01-SEP-03
10.57.36.642000 AM
01-SEP-03 02.57.48.549000 PM -03:00 01-SEP-03
10.57.48.549000 AM
Just when you thought you knew where you were, Oracle has implemented time zones to totally zone us out. Come along and let's figure where we are on this great planet.
A few articles back I wrote on a comparison between the DATE datatype and the TIMESTAMP datatype. This article goes one step further and explores Oracle's TIME ZONE feature of the TIMESTAMP datatype. In particular, Oracle has added the "WITH TIME ZONE" and the "WITH LOCAL TIME ZONE" to the TIMESTAMP datatype.
Valid Time Zones
You have two options when setting which time zone the database belongs to. You can either qualify it as a displacement from GMT/UTC in the format of 'hh:mm' or you can specify it as a name that has an entry in the V$TIMEZONE table. Listing 1 shows the SQL I used to display the valid time zone name in the Mountain Standard Time Zone.
Listing 1
Show valid time zone names for MST
SQL> select tzname,tzabbrev
from V$TIMEZONE_NAMES
where tzabbrev = 'MST'
TZNAME TZABBREV
------------------------- ----------
America/Denver MST
America/Edmonton MST
America/Ensenada MST
America/Mazatlan MST
America/Mexico_City MST
America/Phoenix MST
America/Regina MST
America/Shiprock MST
America/Tijuana MST
Canada/East-Saskatchewan MST
Canada/Mountain MST
Canada/Saskatchewan MST
Europe/Moscow MST
Mexico/BajaNorte MST
Mexico/BajaSur MST
Mexico/General MST
MST MST
MST7MDT MST
Navajo MST
US/Arizona MST
US/Mountain MST
W-SU MST
DBTIMEZONE
At the core of time zones is the database time zone. You can look at the time zone that was selected at database creation by issuing the SQL in Listing 2. If you want to change the DBTIMEZONE you will need to issue an ALTER DATBASE command such as in Listing 3. In order for the new DBTIMEZONE to take effect, you must bounce the database. In addition, if you have any data type columns that are of the TIMESTAMP with TIME ZONE defined, you will not be able to reset the DBTIMEZONE. After bouncing the database, you can issue the SQL in Listing 4 to validate that the change has taken place. If you wanted to switch back to the "hh:mm" format for DBTIMEZONE, just issue the SQL in Listing 5.
Listing 2
Check the database time zone
SQL> select DBTIMEZONE from dual;
DBTIME
------
-07:00
Listing 3
Changing the database time zone
SQL> ALTER database SET TIME_ZONE = 'America/Denver';
Database altered.
Listing 4
Validate the change in DBTIMEZONE
SQL> select DBTIMEZONE from dual;
DBTIMEZONE
---------------
America/Denver
Listing 5
Switch back DBTIMEZONE to hh:mm format
SQL> ALTER database SET TIME_ZONE = '-07:00';
SESSIONTIMEZONE
If you do not want to use the database time zone, Oracle gives you the option to set the time zone at the session level. Issue the SQL in Listing 6 if you want a different time zone for the current session to which you are connected. You can check the session time zone by issuing the SQL in Listing 7.
Listing 6
Set time zone at the session level
SQL> alter session set TIME_ZONE='-03:00';
Session altered.
Listing 7
Check session level time zone
SQL> select SESSIONTIMEZONE from dual;
SESSIONTIMEZONE
-------------------------------------------------
-03:00
SYSTIMESTAMP
Just as there is a call to SYSDATE to get the current system date and time, there is a call to get the current system date, time and time zone. The data type returned is of TIMESTAMP WITH TIME ZONE. Issue the SQL in Listing 8 to get the current system time information.
Listing 8
Get current system timestamp with time zone information
SQL> select SYSTIMESTAMP from dual;
SYSTIMESTAMP
-----------------------------------------------
01-SEP-03 10.53.13.574000 AM -07:00
CURRENT_TIMESTAMP
The counter part of the SYSTIMESTAMP function for session current date and time is the CURRENT_TIMESTAMP function call. This will return what the current time stamp of the session is in relation to the session time zone (SESSIONTIMEZONE). Therefore, if we have the session time zone as defined in Listing 6, we can check the timestamp of the session by issuing the SQL in Listing 9.
Listing 9
Local timestamp for session
SQL> select CURRENT_TIMESTAMP from dual;
CURRENT_TIMESTAMP
-------------------------------------------------
01-SEP-03 02.53.33.753000 PM –03:00
TIMESTAMP datatype with TIME ZONE Information
At the heart of storing time zone information within a table, Oracle has defined the TIMESTAMP data type. This is Oracle's great new hope for giving the old DATE datatype a more granular mechanism of holding not only date and time information but also fractional seconds. Look at A Comparison of Oracle's DATE and TIMESTAMP Datatypes for a discussion of this databtype. For the remainder of this article and for the purposes of exploiting the time zone options for the TIMESTAMP datatype, I have created a table as defined in Table 1. In Listing 10, I have created a quick example of how the TIMESTAMP WITH TIME ZONE and TIMESTAMP WITH LOCAL TIME ZONE datatypes will behave when used to store information. To begin with I have set the DBTIMEZONE and SESSION TIMEZONE to be the same value '-07:00'. I then insert into the DATE_TABLE the value of a system time stamp. I then change the time zone for the current session only to be '-03:00'. This will set the current session four hours ahead of the database time zone. I then insert into the DATE_TABLE a row that will hold the current session timestamp. The main idea to grasp here is that the column with datatype TIMESTAMP WITH TIME ZONE stores and displays the explicit time supplied from the INSERT statement. The column with datatype TIMESTAMP WITH LOCAL TIME ZONE stores the explicit time supplied but will display a value that is relative to the current session time zone. This means that if you want hard and fast TIMESTAMPS with time zone information stored, you should use the TIMESTAMP WITH TIME ZONE datatype. If you are concerned more with giving date and time information to customers in different time zones and represented in their local time, you should use the TIMESTAMP WITH LOCAL TIME ZONE datatype.
Table 1:
Create table with different TIMESTAMP columns
create table date_table (
time_stamp_tz TIMESTAMP WITH TIME ZONE,
time_stamp_ltz TIMESTAMP WITH LOCAL TIME ZONE);
LISTING 10
Inserting SYSTIMESTAMP into DATE_TABLE
SQL> select dbtimezone,sessiontimezone from dual;
DBTIMEZONE SESSIONTIMEZONE
---------- ----------------
-07:00 -07:00
SQL> insert into date_table values (SYSTIMESTAMP,SYSTIMESTAMP);
1 row created.
SQL> alter session set time_zone='-03:00';
Session altered.
SQL> select dbtimezone,sessiontimezone from dual;
DBTIMEZONE SESSIONTIMEZONE
---------- ----------------
-07:00 -03:00
SQL> insert into date_table values (LOCALTIMESTAMP,LOCALTIMESTAMP );
1 row created.
SQL> select time_stamp_tz, time_stamp_ltz from date_table;
TIME_STAMP_TZ TIME_STAMP_LTZ
------------------------------------- ------------------------------
01-SEP-03 10.57.36.642000 AM -07:00 01-SEP-03 02.57.36.642000 PM
01-SEP-03 02.57.48.549000 PM -03:00 01-SEP-03 02.57.48.549000 PM
SQL> alter session set time_zone='-07:00';
Session altered.
SQL> select time_stamp_tz, time_stamp_ltz from date_table;
TIME_STAMP_TZ TIME_STAMP_LTZ
------------------------------------- ------------------------------
01-SEP-03 10.57.36.642000 AM -07:00 01-SEP-03
10.57.36.642000 AM
01-SEP-03 02.57.48.549000 PM -03:00 01-SEP-03
10.57.48.549000 AM
Unable To View Status Diagram [ID 746806.1]
Unable To View Status Diagram [ID 746806.1]
--------------------------------------------------------------------------------
Modified 29-DEC-2008 Type PROBLEM Status MODERATED
In this Document
Symptoms
Cause
Solution
References
--------------------------------------------------------------------------------
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.
Applies to:
Oracle Workflow Cartridge - Version: 11.5.9 to 12.0.6
This problem can occur on any platform.
Symptoms
When clicked on the Status diagram following message appears "You have encountered an unexpected error. Please contact the System Administrator for assistance."
The issue can be reproduced at will with the following steps:
1. Log in to Sysadmin
2. Select Workflow Adminstrator Responsbility
3. Select status monitor
4. Provide the details of the item type
5. Click on status diagram. Now it shows error page.
Setting FND Diagnostics profile option for the user who is seeing the error message is changing "You have encountered an unexpected error. Click here for details. Please contact the System Administrator for assistance."
When pressed on the Click Here link the stack error trace shows:
oracle.apps.fnd.framework.OAException: java.lang.NullPointerException
...
## Detail 0 ##
java.lang.NullPointerException
java.lang.NullPointerException
or
## Detail 0 ##
java.lang.NullPointerException
at java.util.Hashtable.get(Hashtable.java:315)
at oracle.apps.fnd.util.OracleTimezone.getTimezoneNameFromCode(OracleTimezone.java:171)
at oracle.apps.fnd.framework.OANLSServices.getTimezoneName(OANLSServices.java:1611)
at oracle.apps.fnd.wf.monitor.webui.GraphMonitorCO.processRequest(GraphMonitorCO.java:107)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:525)
Cause
Server Timezone profile option at Site level is not set.
The Null Pointer Exception is occurring from within OA Framework's code which Workflow's code is calling.
iAS need to instantiate the class file and if it finds the profile to be null it throws a null pointer exception. The JSP is then cached once the profile is set afterwords and we will just be reading the cached class. The error started occurring after making EBS timezone aware so the profile need to be set to the timezone of the database to provide the off set calculation for user connections.
Solution
1. Set the profile option Server Timezone at Site level (should be set to the value of database timezone)
2. Bounce the Apache Server
--------------------------------------------------------------------------------
Modified 29-DEC-2008 Type PROBLEM Status MODERATED
In this Document
Symptoms
Cause
Solution
References
--------------------------------------------------------------------------------
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.
Applies to:
Oracle Workflow Cartridge - Version: 11.5.9 to 12.0.6
This problem can occur on any platform.
Symptoms
When clicked on the Status diagram following message appears "You have encountered an unexpected error. Please contact the System Administrator for assistance."
The issue can be reproduced at will with the following steps:
1. Log in to Sysadmin
2. Select Workflow Adminstrator Responsbility
3. Select status monitor
4. Provide the details of the item type
5. Click on status diagram. Now it shows error page.
Setting FND Diagnostics profile option for the user who is seeing the error message is changing "You have encountered an unexpected error. Click here for details. Please contact the System Administrator for assistance."
When pressed on the Click Here link the stack error trace shows:
oracle.apps.fnd.framework.OAException: java.lang.NullPointerException
...
## Detail 0 ##
java.lang.NullPointerException
java.lang.NullPointerException
or
## Detail 0 ##
java.lang.NullPointerException
at java.util.Hashtable.get(Hashtable.java:315)
at oracle.apps.fnd.util.OracleTimezone.getTimezoneNameFromCode(OracleTimezone.java:171)
at oracle.apps.fnd.framework.OANLSServices.getTimezoneName(OANLSServices.java:1611)
at oracle.apps.fnd.wf.monitor.webui.GraphMonitorCO.processRequest(GraphMonitorCO.java:107)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:525)
Cause
Server Timezone profile option at Site level is not set.
The Null Pointer Exception is occurring from within OA Framework's code which Workflow's code is calling.
iAS need to instantiate the class file and if it finds the profile to be null it throws a null pointer exception. The JSP is then cached once the profile is set afterwords and we will just be reading the cached class. The error started occurring after making EBS timezone aware so the profile need to be set to the timezone of the database to provide the off set calculation for user connections.
Solution
1. Set the profile option Server Timezone at Site level (should be set to the value of database timezone)
2. Bounce the Apache Server
Monday, May 3, 2010
HotBackup Script
HotBackup Script [ID 221630.1]
--------------------------------------------------------------------------------
Modified 20-MAY-2007 Type SCRIPT Status PUBLISHED
Overview:
---------
This script is able to take a backup online.
Instructions:
-------------
>> Create the bkp.sql file with the informations bellow:
Rem The connection with the server should be with a SYSDBA user
conn / as sysdba
set feed off
set serveroutput on
set linesize 300
Rem Verify the directory where the script .sql to be created, will be executed.
spool %ORACLE_BASE%\admin\scripts\hotbkp.sql
exec HotBkp;
spool off
set feed on
Rem Check the location of the SPOOL file because it will be called now
exit;
--------------------------------------------------------------------------------
>> Create a CodHotBkp.sql file with the commands bellow:
create or replace procedure HotBkp
is
/* cursor to capture Tablespaces that it will be put in the Backup, accessing Temporary Tablespaces Managed Locally */
cursor cTbs is
select ts# tId, name tName
from v$tablespace
where ts# not in (select distinct ts# from v$tempfile);
/* Cursor to capture Data Files that it will be put in the Backup */
cursor cDtfl is
select ts# tId, name dName, substr(name,
instr(name,decode('\',NULL,'/','\'),-1)+1,
instr(name,'.',-1)-instr(name,decode('\',NULL,'/','\'),-1)-1) DestName
from v$datafile;
/* Default backup directory. It should be compatible with your environment. */
CBkpDir constant varchar2(100):='c:\orabkp\';
/* Default extension's backup files */
CBkpExt constant varchar2(4):='.bkp';
/* Default extension's control file logical backup */
CBkpCtflExt constant varchar2(4):='.sql';
/* Files name generated throught Logical Backup and Control Files's Backup Online */
CBkpCtfl constant varchar2(7):='control';
VSpid varchar2(100);
VUdump varchar2(100);
begin
dbms_output.enable(50000);
dbms_output.put_line('spool '||CBkpDir||'hotbkp.log');
/* Capture the start hour of Backup Online execution */
dbms_output.put_line('select to_char(sysdate, ''dd/mm/rrrr hh24:mi:ss'')
Start_Time'||chr(10)||
'from dual;');
/* Starting the LOOP to take a Tablespaces's Backup Online */
for rTbs in cTbs loop
dbms_output.put_line('alter tablespace '||rTbs.tName||' begin backup;');
for rDtfl in cDtfl loop
if (rDtfl.tId=rTbs.tId) then
dbms_output.put_line('HOST ocopy '||rDtfl.dName||'
'||CBkpDir||rDtfl.DestName||CBkpExt);
end if;
end loop;
dbms_output.put_line('alter tablespace '||rTbs.tName||' end backup;');
dbms_output.put_line('alter system checkpoint;');
end loop;
select value into VUdump from v$parameter
where lower(name) = 'user_dump_dest';
select '*'||p.spid||'*.trc' into VSpid from v$process p, v$session s
where s.paddr=p.addr and s.audsid=userenv('SessionId') and s.username='SYS' and
s.status='ACTIVE';
dbms_output.put_line('alter database backup controlfile to trace;');
dbms_output.put_line('HOST copy '||VUdump||'\'||VSpid||'
'||CBkpDir||CBkpCtfl||CBkpCtflExt);
dbms_output.put_line('alter database backup controlfile to
'''||CBkpDir||CBkpCtfl||CBkpExt||''';');
dbms_output.put_line('alter system archive log current;');
/* Capture the end hour of Backup Online execution */
dbms_output.put_line('select to_char(sysdate, ''dd/mm/rrrr hh24:mi:ss'')
End_Time'||chr(10)||
'from dual;');
/* Closing the log */
dbms_output.put_line('spool off');
end;
--------------------------------------------------------------------------------
Modified 20-MAY-2007 Type SCRIPT Status PUBLISHED
Overview:
---------
This script is able to take a backup online.
Instructions:
-------------
>> Create the bkp.sql file with the informations bellow:
Rem The connection with the server should be with a SYSDBA user
conn / as sysdba
set feed off
set serveroutput on
set linesize 300
Rem Verify the directory where the script .sql to be created, will be executed.
spool %ORACLE_BASE%\admin\scripts\hotbkp.sql
exec HotBkp;
spool off
set feed on
Rem Check the location of the SPOOL file because it will be called now
exit;
--------------------------------------------------------------------------------
>> Create a CodHotBkp.sql file with the commands bellow:
create or replace procedure HotBkp
is
/* cursor to capture Tablespaces that it will be put in the Backup, accessing Temporary Tablespaces Managed Locally */
cursor cTbs is
select ts# tId, name tName
from v$tablespace
where ts# not in (select distinct ts# from v$tempfile);
/* Cursor to capture Data Files that it will be put in the Backup */
cursor cDtfl is
select ts# tId, name dName, substr(name,
instr(name,decode('\',NULL,'/','\'),-1)+1,
instr(name,'.',-1)-instr(name,decode('\',NULL,'/','\'),-1)-1) DestName
from v$datafile;
/* Default backup directory. It should be compatible with your environment. */
CBkpDir constant varchar2(100):='c:\orabkp\';
/* Default extension's backup files */
CBkpExt constant varchar2(4):='.bkp';
/* Default extension's control file logical backup */
CBkpCtflExt constant varchar2(4):='.sql';
/* Files name generated throught Logical Backup and Control Files's Backup Online */
CBkpCtfl constant varchar2(7):='control';
VSpid varchar2(100);
VUdump varchar2(100);
begin
dbms_output.enable(50000);
dbms_output.put_line('spool '||CBkpDir||'hotbkp.log');
/* Capture the start hour of Backup Online execution */
dbms_output.put_line('select to_char(sysdate, ''dd/mm/rrrr hh24:mi:ss'')
Start_Time'||chr(10)||
'from dual;');
/* Starting the LOOP to take a Tablespaces's Backup Online */
for rTbs in cTbs loop
dbms_output.put_line('alter tablespace '||rTbs.tName||' begin backup;');
for rDtfl in cDtfl loop
if (rDtfl.tId=rTbs.tId) then
dbms_output.put_line('HOST ocopy '||rDtfl.dName||'
'||CBkpDir||rDtfl.DestName||CBkpExt);
end if;
end loop;
dbms_output.put_line('alter tablespace '||rTbs.tName||' end backup;');
dbms_output.put_line('alter system checkpoint;');
end loop;
select value into VUdump from v$parameter
where lower(name) = 'user_dump_dest';
select '*'||p.spid||'*.trc' into VSpid from v$process p, v$session s
where s.paddr=p.addr and s.audsid=userenv('SessionId') and s.username='SYS' and
s.status='ACTIVE';
dbms_output.put_line('alter database backup controlfile to trace;');
dbms_output.put_line('HOST copy '||VUdump||'\'||VSpid||'
'||CBkpDir||CBkpCtfl||CBkpCtflExt);
dbms_output.put_line('alter database backup controlfile to
'''||CBkpDir||CBkpCtfl||CBkpExt||''';');
dbms_output.put_line('alter system archive log current;');
/* Capture the end hour of Backup Online execution */
dbms_output.put_line('select to_char(sysdate, ''dd/mm/rrrr hh24:mi:ss'')
End_Time'||chr(10)||
'from dual;');
/* Closing the log */
dbms_output.put_line('spool off');
end;
Subscribe to:
Posts (Atom)