Probably those two files saved during backup (compression going on at the moment of capture) so I would say warning is real and you could also ignore it too.
If you are able to reproduce this with 7.3.1 (so update is required) and prove that message is incorrect as file is not open (on Solaris you can easily check that with system tools) and the you have material - otherwise I don't trust what cu says. Try to check it out yourself.
Error != warning. I didn't say it was error, I said it was warning.
Also it did say that size shrunk - this means it did change during the save of the file. This usually happens with live DBs, logs or any other file being operated at that time. I would say from error you have listed that gz archive was being updated or created at the time when backup was trying to pick it up. If you get that each time, I would write directive to skip it up.
Do mminfo on /raid4 for that backup instance and see what does it get repiorted for totalsize/sumsize pair. Then you can do nsrinfo for given nsavetime.
ble1
4 Operator
•
14.4K Posts
0
June 21st, 2006 07:00
ble1
4 Operator
•
14.4K Posts
0
June 21st, 2006 08:00
If you are able to reproduce this with 7.3.1 (so update is required) and prove that message is incorrect as file is not open (on Solaris you can easily check that with system tools) and the you have material - otherwise I don't trust what cu says. Try to check it out yourself.
mg115301
1 Rookie
•
100 Posts
0
June 21st, 2006 08:00
I talk with cu and he say no. The files are create
060614
And the savset was from 06:16:19
Cu say, that after this time stamp, this file was not updatet or create.
--- Successful Save Sets ---
epbup: /raid4 level=full, 4062 MB 06:16:19 109 files
* : Warning - `/raid4/online/Redmark/d9.ORA2@ora.060614.gz' size shrunk during save
* : Expected 4294967295 bytes for `/raid4/online/Redmark/d9.ORA2@ora.060614.gz', got 4003610249 bytes
* : Warning - `/raid4/online/Redmark/d9.ORA3@ora.060614.gz' size shrunk during save
* : Expected 4294967295 bytes for `/raid4/online/Redmark/d9.ORA3@ora.060614.gz', got 4049440815 bytes
* : Warning - `/raid4/online/Redmark/d9.ORA4@ora.060614.gz' size grew during save
ble1
4 Operator
•
14.4K Posts
0
June 21st, 2006 08:00
Also it did say that size shrunk - this means it did change during the save of the file. This usually happens with live DBs, logs or any other file being operated at that time. I would say from error you have listed that gz archive was being updated or created at the time when backup was trying to pick it up. If you get that each time, I would write directive to skip it up.
mg115301
1 Rookie
•
100 Posts
0
June 21st, 2006 08:00
Is this error real, why we can ignore it?
Cu have this error new. But I think it is not normal to see one error message and ignore it.
And why EBS think, alle files have the same size?
--- Successful Save Sets ---
epbup: /raid4 level=full, 4062 MB 06:16:19 109 files
* : Warning - `/raid4/online/Redmark/d9.ORA2@ora.060614.gz' size shrunk during save
* : Expected 4294967295 bytes for `/raid4/online/Redmark/d9.ORA2@ora.060614.gz', got 4003610249 bytes
* : Warning - `/raid4/online/Redmark/d9.ORA3@ora.060614.gz' size shrunk during save
* : Expected 4294967295 bytes for `/raid4/online/Redmark/d9.ORA3@ora.060614.gz', got 4049440815 bytes
* : Warning - `/raid4/online/Redmark/d9.ORA4@ora.060614.gz' size grew during save
The data are more then 4 GB for this saveset.
mg115301
1 Rookie
•
100 Posts
0
June 22nd, 2006 01:00
I order ls -lu and fuser, but this files are not longer on the system
I say to him, that we cannot realy say, that not any process have his finger on the file, by this backup.
The error comes up only one time.
But he ask me, why the saveset think, the backup is 4062MB ?
And why the file all 4294967295 bytes?
Cu say, that the size is not correct and the saveset must larger then 4062MB.
Succeeded with warning(s): epbup
Start time: Sat Jun 17 11:30:00 2006
End time: Sun Jun 18 03:13:46 2006
--- Successful Save Sets ---
epbup: /raid4 level=full, 4062 MB 06:16:19 109 files
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
* epbup:/raid3 1 retry attempted
epbup: /raid3 level=full, 262 GB 05:19:38 3758263 files
epbup: /raid2 level=full, 290 GB 08:46:07 11153 files
epbup: /raid1 level=full, 814 GB 15:37:21 6237770 files
epbup: /nsr level=full, 18 MB 00:00:17 1690 files
epbup: /raid3_alt level=full, 2 KB 00:00:02 3 files
epbup: /raid2_alt level=full, 13 GB 00:14:53 10 files
epbup: /raid1_alt level=full, 2 KB 00:00:02 3 files
epbup: /var level=full, 175 MB 00:00:29 7397 files
epbup: / level=full, 7441 MB 00:09:06 123302 files
epbup: index:epbup level=full, 18 GB 00:06:12 799 files
epbup: bootstrap level=full, 6799 KB 00:00:09 1393 files
ble1
4 Operator
•
14.4K Posts
0
June 22nd, 2006 02:00
mg115301
1 Rookie
•
100 Posts
0
June 22nd, 2006 23:00
I close the case. My cu will look, this problem comes back again.
But I think the problem is his script.
Mike