DB backup issue

[Former Member]

Hi All,

I have a problem in database backup.

The next extent, updatestats, and also the checkdb always completed with warning.

For next extent, the highlight warning is <b>No tables/indexes found to check and adapt next extent</b>. For this one, I think it is acceptable.

But I confuse about the update stats, it's warning log is like this :

BR0871W Pool or cluster table selected to check/collect statistics: SAPR3S.EPIDXB

BR0871W Pool or cluster table selected to check/collect statistics: SAPR3S.EPIDXC

BR0871W Pool or cluster table selected to check/collect statistics: SAPR3S.GLSP

BR0871W Pool or cluster table selected to check/collect statistics: SAPR3S.GLTP

BR0871W Pool or cluster table selected to check/collect statistics: SAPR3S.KAPOL

BR0871W Pool or cluster table selected to check/collect statistics: SAPR3S.KOCLU

BR0871W Pool or cluster table selected to check/collect statistics: SAPR3S.M_IFLM

BR0871W Pool or cluster table selected to check/collect statistics: SAPR3S.VBCLU

BR0871W Pool or cluster table selected to check/collect statistics: SAPR3S.VBFCL

.....

.....

BR0986W Index SAPR3S.SEOIMPLREL~0 is unbalanced - please rebuild the index

Whats the problem with my index (SAPR3S) ?

<b>And the checkDB has warning like this :</b>

BR0970W Database administration alert - level: WARNING, type: CRITICAL_FILE, object: /oracle/RP1/sapdata1/system_1/system.data1, value: (max_size) 9676800 KB (> 9431280 KB)

.....

BR0973W Database operation alert - level: WARNING, operation: adwpeota.cds, time: 2007-11-15 03.35.02, condition: Last archive log backup failed with rc = 3

In DB12 the redo logs backup also triggered more than 1 time. So the Verify DB operation always error with rc 0003.

Does anyone know what the causes and how to solve this ?

Thx.

Regards,

casper.

[former_member193294 · Accepted solution]

Hi casper,

regarding your warnings of the statistics please check:

Note 411773 - Warning BR871W for update statistics in BRCONNECT 6.10

The message:BR0970W Database administration alert - level: WARNING, type: CRITICAL_FILE, object: /oracle/RP1/sapdata1/system_1/system.data1, value: (max_size) 9676800 KB (> 9431280 KB) indicates that the potential size of your file is bigger than the available space in your filesystem. You have either to edit the datafile and lower the max extend size , after calculating how much your real free space on the particular filesystem is or extend your filesystem.

You failed archive redo log file backup would need more investigation from your side.

A general SAP Note which might be helpful for DB13 errors/warnings is: 442395

Best regards,

Loukas

[Former Member]

Hi,

<b>Regarding the BR0871 Warning</b>

The tables issued are entered in the DBSTATC tax table with ACTIVE indicator "A" or "P", even though they are pool or cluster tables. Tables such as these are not usually permitted to have any statistics.

Use Transaction DB21 to change the ACTIVE flag for these tables to "R". Statistics are then only created for these for a short period of time, saved in Table DBSTATTORA and then deleted immediately afterwards.

However, if you are absolutely certain that the table should have statistics, set the customer flag in DBSTATC for the table.

Ref Note 411773 - Warning BR871W for update statistics in BRCONNECT

<b>Regarding BR0986 warning.</b>:

In BRTOOLS---->Segment Management---->Rebuild Index and rebuild the index SEOIMPLREL~0.

<b>Regarding the CRITICAL_FILE</b>

If the disk space available is less than

MAX_SIZE and AUTO_EXTENSION is active,a CRITICAL_FILE alert is raised, as a file system overflow could occur if Oracle would extend the data file.

To avoid this more physical space has to be allocated

Pl award suitably if resolved.