Operating System - HP-UX
1748236 Members
3648 Online
108759 Solutions
New Discussion юеВ

Re: Problem with extending oracle tablespaces after certain standard Patch installation

 
arun khatwani
Frequent Advisor

Problem with extending oracle tablespaces after certain standard Patch installation

Hi,

On one of HPUX 11.31 system the below patches were installed.
xxxxx:/root> swlist | grep -i fea
FEATURE11i B.11.31.1003.347a Feature Enablement Patches for HP-UX 11i v3, March 2010
xxxxx:/root> swlist | grep -i hwe
HWEnable11i B.11.31.1003.347a Hardware Enablement Patches for HP-UX 11i v3, March 2010
xxxxxx:/root> swlist | grep -i qpk
QPKAPPS B.11.31.1003.347a Applications Patches for HP-UX 11i v3, March 2010
QPKBASE B.11.31.1003.347a Base Quality Pack Bundle for HP-UX 11i v3, March 2010


xxxxx:/root> swlist | grep -i onc
ONCplus B.11.31.09.01 ONC+ 2.3



xxxxxx:/root> swlist | grep -i -e Base-VxFS-50 -e BaseLVM -e B3929FB
B3929FB B.05.00.01 OnlineJFS for Veritas File System 5.0 Bundle
Base-VxFS-50 B.05.00.01 Veritas File System Bundle 5.0 for HP-UX
BaseLVM B.11.31.0903 Logical Volume Manager

Now Oracle DBA are mentioning that due to this patches installation they are facing the below error

SQL> alter database datafile '/oracle/P01/sapdata6/stabd_24/stabd.data24' resize 7000M;
alter database datafile '/oracle/P01/sapdata6/stabd_24/stabd.data24' resize 7000M
*
ERROR at line 1:
ORA-01237: cannot extend datafile 438
ORA-01110: data file 438: '/oracle/P01/sapdata6/stabd_24/stabd.data24'
ORA-19502: write error on file "/oracle/P01/sapdata6/stabd_24/stabd.data24", blockno 768256 (blocksize=8192)
ORA-27072: File I/O error
HPUX-ia64 Error: 22: Invalid argument
Additional information: 4
Additional information: 768256
Additional information: -1

Is the above error is due to these patches installation
Kindly suggest to resolve this issues.
4 REPLIES 4
Prasanth V Aravind
Trusted Contributor

Re: Problem with extending oracle tablespaces after certain standard Patch installation

before debugging to patches & its buggs .. ask some some questions to your DBA...

what is the current size of /oracle/P01/sapdata6/stabd_24/stabd.data24

does dba facing issue only on this table space ??

what about the remaining tables ??it it able to increase space on them ?

what is the filesyetms/inode utilizations ?

how he get to know, issue is because of patch installation

did you installed same patches on any other servers ?



GUdluck
Prasanth
Steven E. Protter
Exalted Contributor

Re: Problem with extending oracle tablespaces after certain standard Patch installation

Shalom,

You may need to relink oracle or back out the patch set.

If the results are consistent on all systems, back out the patch set, if Oracle support can not help you resolve the issue.

We are in process of installing the September 2009 11.31 patch set on Oracle systems and have not encountered similar problems.

I've seen patches impact Oracle functionality before and relink usually helps. Also if you have HP-UX software support, the HP Response Center has an Oracle Liaison group that will work with Oracle to assist in resolving the issue.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
singh sanjeev
Trusted Contributor

Re: Problem with extending oracle tablespaces after certain standard Patch installation

check whether there is suffient space in file system or not....it seems space problem on file system

also refer syslog for any clue
Sanjeev Singh
TTr
Honored Contributor

Re: Problem with extending oracle tablespaces after certain standard Patch installation

> write error on file "/oracle/P01/sapdata6/stabd_24/stabd.data24", blockno 768256 (blocksize=8192)

This looks like a disk write error to me.

First check if there is room in the filesystem to grow that oracle file by the specified amount. The DBA may be trying to extend the file beyond the filesystem size.

If there is space, there is probably a disk write error. Try to create or copy files in that same path (same filessytem) from the OS and see if you get the similar errors.

The disk error may not be related to the patches, it was probably always there but that specific spot on the disk was never written to until now.