Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

TDP RMAN error

Status
Not open for further replies.

avalon111

IS-IT--Management
Feb 11, 2010
10
NL
When performing a backup of an instance, this error is seen;

released channel: Chan1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on Chan1 channel at 05/29/2010 12:30:29
ORA-27206: requested file not found in media management catalog
ORA-19502: write error on file "<instance_gslestuo_1_1", blockno 1 (blocksize=1024)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
ANS1017E (RC-50) Session rejected: TCP/IP connection failure


However when available backups are checked through Rman, it looks like all backups of this database terminate normally.
TSM-info:

tdpoconf SHOWENVironment -TDPO_OPTfile=/data/oracle/<instance>/admin/tivoli/tdpo.opt

IBM Tivoli Storage Manager for Databases:
Data Protection for Oracle
Version 5, Release 2, Level 0.0
(C) Copyright IBM Corporation 1997, 2003. All rights reserved.


TDP FOR ORACLE INFORMATION
Version: 5
Release: 2
Level: 0
Sublevel: 0
Platform: 64bit TDP Oracle HP

Looking at the platform, I can see numerous entries of following in dsmerror.log, but the times don't match up ;

31.05.2010 06:04:08 Error -1 starting session thread.
31.05.2010 06:04:08 Maximum number of threads exceeded.
31.05.2010 06:04:08 Error -1 starting session thread.
31.05.2010 06:04:08 Maximum number of threads exceeded.
31.05.2010 06:04:08 Error -1 starting session thread.

The nearest I can get in describing this error relates only to the Server product, not the client;


as being related to the kernel thread max_thread_proc

But this is already set to 4096 and nproc is pretty high at 6000

The thread error might be a red herring, so anyone have any insight into the RMAN specific error, or the thread error seen in dsmerror.log (and can they be related) I'd be very grateful.

avalon
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top