BRCONNECT & BRTOOLS conflicting max size value.

[Former Member]

Hi,

I have a conflicting max_size value for tst.data1 between checkDB (DB13) and brtools. The checkDB log shows that the max size is 5427200 KB while brtools shows 10240000. (refer to list below) checkDB shows that tst.data1 is already critical but brtools says the opposit. How can I correct this?

A. From checkDB log:

===========================================================

BR0970W Database administration alert - level: WARNING, type: CRITICAL_FILE, object: /oracle/TST/sapdata3/tst_1/tst.data1, value: (max_size) 5427200 KB (> 4914940 KB)

B. From brtools:

===========================================================

Pos. Tablespace Status Type File

Id. Size[KB] Device Back. AuExt. MaxSize[KB] IncrSize[KB]

1 - PSAPTST ONLINE FILE /oracle/TST/sapdata3/tst_1/tst.data1

3 4812800 1073938442 NO YES 10240000 20480

We are on ECC5, Oracle 9206 and HP-UX 11i.

rgds,

krbas.

[Former Member · Accepted solution]

Hello,

CRITICAL_FILE Examines the data files with an activated auto extend feature. A check is made to see whether the file system can be brought to overflow, due to the existing parameter setting (NEXT and MAXSIZE) during the automatic file extension.

The value of MAXSIZE (10240000)is the maximum size to which the file can automatically extend.

So the space that it has to grow 5427200 KB is greater than the size available 4914940 KB in system where it resides.

Make it no auto extensible and add datafile or File system size or change alert of check Dbs.

Vinod

[former_member204746 · Accepted solution]

Vinod provided you with an excellent answer.

so, in you case:

datafile /oracle/TST/sapdata3/tst_1/tst.data1 needs 5427200 KB on disk to grow but you unfortunately only have 4914940 KB left on this disk.

you file is probably sized 4530000KB and needs 5427200KB to read 10240000KB.

possible solutions:

1. change max_size to a lower value (and consider adding a datafile on another disk)

2. add disk space

3. move datafile elsewhere

Good luck.

[Former Member]

Hi Experts,

I' running ECC5.0 with Oracle.

While CheckDB in db13 I'm recieveign following error from few days.

BR0981W Not enough disk space for the total maximum size 90000.000 MB of 9 files of tablespace PSAP<SID> on disk device 5578786, missing at least 46664.094 MB

BR0981W Not enough disk space for the total maximum size 40000.000 MB of 4 files of tablespace PSAP<SID>640 on disk device 5578786, missing at least 4064.094 MB

BR0981W Not enough disk space for the total maximum size 50000.000 MB of 5 files of tablespace PSAP<SID>640 on disk device 5578783, missing at least 6934.141 MB

BR0981W Not enough disk space for the total maximum size 50000.000 MB of 5 files of tablespace PSAP<SID>640 on disk device 5578784, missing at least 5729.336 MB

I've tried to increase the Tablespace thru BRtools, but after I'm getting same error with more diskspace required:

BR0981W Not enough disk space for the total maximum size 90000.000 MB of 9 files of tablespace PSAP<SID> on disk device 5578786, missing at least 51666.562 MB

BR0981W Not enough disk space for the total maximum size 50000.000 MB of 5 files of tablespace PSAP<SID>640 on disk device 5578786, missing at least 14066.562 MB

BR0981W Not enough disk space for the total maximum size 50000.000 MB of 5 files of tablespace PSAP<SID>640 on disk device 5578783, missing at least 6934.141 MB

BR0981W Not enough disk space for the total maximum size 50000.000 MB of 5 files of tablespace PSAP<SID>640 on disk device 5578784, missing at least 5729.336 MB

Pl. anyone suggest to solve the Problem.

[former_member193294]

Hi Prakash,

the MAXSIZE which you have defined (for instance) for the 9 files of 90000.000 MB is higher than the available space in your filesystem.

You should requests from your system admin more space or define lower MAXSIZE for the respective files.

Rgds,

Loukas

[Former Member]

Hi Kbas,

DB13 and BR tool checks differently, go to tablespace thru OEM tool or any other tool and see the properties uncheck the autoextend on feature.

Then come back to DB13 execute check database from DB13 you will not see the

warning/error in DB13 checkdb log.

When Autoextend on enabled for the tablespace, the DB13 checks whether the

next size of the extent is enough in comparisn with the autoextention size of the

the tablespace, if the size of autoextention is smaller than the size required, you

will get the warning message in DB13.

Hope this will help you.

Regards

Manohar

[Former Member]

thanks all.

kbas