When checking SunExadataX2-2 all-in-one, the following error occurs in the alert file: MonJun0922: 19: Warning (incident449691): ORA-00600: internalerrorcode, arguments: [k
2014-06-10 when checking Sun Exadata X2-2 all-in-one, the following error appears in the alert file: mon Jun 09 22:19:29 2014 Errors in file/u01/app/oracle/diag/rdbms/mcsdb/MCSDB2/trace/MCSDB2_ora_13405.trc (incident = 449691): ORA-00600: internal errorcode, arguments: [k
2014-06-10 when checking Sun Exadata X2-2 all-in-one, the following error appears in the alert file:
Mon Jun 09 22:19:29 2014
Errors in file/u01/app/oracle/diag/rdbms/mcsdb/MCSDB2/trace/MCSDB2_ora_13405.trc (incident = 449691 ):
ORA-00600: internal errorcode, arguments: [krbbsThrottle _ zero_total_size], [90790400], [120070512], [], [], [], [], [], [], [], [], [], [], []
Incident details in:/u01/app/oracle/diag/rdbms/mcsdb/MCSDB2/incident/incdir_449691/MCSDB2_ora_13405_i449691.trc
Mon Jun 09 22:19:49 2014
Dumping diagnostic data indirectory = [cdmp_20140609221949], requested by (instance = 2, osid = 13405), summary = [incident = 449691].
Mon Jun 09 22:19:49 2014
Use ADRCI or SupportWorkbench to package the incident.
See Note 411.1 at My OracleSupport for error and packaging details.
Deleted Oracle managed file + RECO_DM01/mcsdb/backupset/2014_06_09/nnndn1_tag2014_06_09_incre1_bak_df_0.560.849820325
Mon Jun 09 22:19:50 2014
Sweep [inc] [449691]: completed
Sweep [inc2] [449691]: completed
Query Oracle Metalink. Result 1:
|
|
|
|
Bug 17025461-ORA-600 [krbbsThrottle _ zero_total_size] on RMAN backup (Doc ID 17025461.8) |
To Bottom |
|
Modified: 14-Mar-2014 Type: PATCH |
|
|
Bug 17025461 ORA-600 [krbbsThrottle _ zero_total_size] on RMAN backup
This note gives a brief overview of bug 17025461.
The content was last updated on: 11-MAR-2014 ClickHereFor details of each of the ps below.
Affects:
|
Product (Component) |
Oracle Server (Rdbms) |
|
Range of versionsBelievedTo be affected |
(Not specified) |
|
VersionsConfirmedAs being affected |
11.2.0.4
11.2.0.3 |
|
Platforms affected |
Generic (all/most platforms affected) |
Fixed:
|
The fix for 17025461 is first supported in |
12.2 (Future Release)
12.1.0.2 (Future Patch Set) |
Interim patches may be available for earlier versions-clickHereTo check.
|
Query Oracle Metalink. Result 2:
|
Bug 9835218-OERI [krbbsThrottle _ zero_total_size] from Exadata RMAN Incremental backup (Doc ID 9835218.8) |
Bug 9835218 OERI [krbbsThrottle _ zero_total_size] fromadata RMAN Incremental backup
This note gives a brief overview of bug9835218.
The content was last updated on: 28-JUN-2013
ClickHereFordetails of each of the ps below.
Affects:
|
Product (Component) |
Oracle Server (Rdbms) |
|
Range of versionsBelievedTo be affected |
Versions> = 11, but BELOW 12.1 |
|
VersionsConfirmedAs being affected |
|
|
Platforms affected |
Generic (all/most platforms affected) |
Fixed:
His issue is fixed in
- 12.1.0.1 (Base Release)
- 11.2.0.2 (Server Patch Set)
- 11.2.0.1 Bundle Patch 6 for Exadata Database
| Symptoms: |
Related: |
- Internal Error May Occur (ORA-600)
- ORA-600 [krbbsThrottle _ zero_total_size]
|
- Exadata
- RMAN (Recovery Manager)
|
Description
An Exadata/SAGE RMAN INCREMENTAL LEVEL 1 backup throws this internal error:
ORA-600 [krbbsThrottle_ zero_total_size] [total] [done]
indicating that blocks backed up [done] is greater then expected [total]
blocks.
Workaround
Specify a backup set piece size MAXPIECESIZE large enough to create just
one backup piece.
|
Please note:The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. For questions about this bug please consult Oracle Support. |
References
Bugs: 9835218 (This link will only work for PUBLISHED bugs)
Note: 245840.1 Information on the ps in this article
Temporary countermeasure: Re-Execute Rman L0 backup
After the L0 backup is re-executed on February 12, the L1 Incremental backup is successfully performed.
Official explanations from Oracle:
Based on our findings, we are suspecting Bug 17025461: EXADATA: ORA-600 [KRBBSTHROTTLE _ ZERO_TOTAL_SIZE] on rman incremental level 1 for this issue.
Possible Workaround:
1) Don't set auto-extend on for datafiles. Create larger datafiles to account for space expansion.
If that is not possible, reduce the possiblity of auto-extending datafiles (by specifying extend size larger value ).
Do not set auto-extended data files. Creating a larger data file requires space expansion. If this is not possible to reduce the possibility of automatic expansion of data files (by specifying a larger scale value)
2) Use higher value of MAXPIECESIZE to prevent possibility of hitting this bug.
Translation: Configure Rman to use a more valuable MAXPIECESIZE to prevent the possibility of hitting this bug
3) Also setting _ disable_cell_optimized_backups = TRUE, may help in avoiding the bug.
You can also set _ disable_cell_optimized_backups = TRUE to avoid bugs.
The patch is available for 11.2.0.3BP17 and the issue is fixed in version 12.2.