NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Robotic status code 238

Robotic status code 238
HOWTO104741 | 2014-11-20
How To | CMS-XML

NetBackup status code: 238

NetBackup status code : 238
HOWTO104153 | 2014-11-20
How To | CMS-XML

STATUS CODE: 238, 671 Occurs during a synthetic backup when the Veritas NetBackup catalog has an inconsistent or corrupted entry.

the database contains conflicting or erroneous entries( 238 ) query for list of component images failed(671)
TECH37238 | 2009-01-02
Technical Solutions | CMS-XML

BUG REPORT: In NetBackup versions 6.5.2 and 6.5.3, attempts to update a policy through the GUI may result in a status code 238

Symptoms : After deactivating or activating a policy, any attempt to make further policy changes results in a status 238 An example is below: The log data shows messages similar to the following:
TECH65993 | 2009-01-02
Technical Solutions | CMS-XML

VMware restore failing with "VMware policy restore error(2820)" due to timeout in bptm child pid "wait for child pid #### timeout"

11:16:23.097 [3616.520] 2 wait_for_sigcld_or_stop_db_restore: waiting for child 11144 to exit, timeout is 300 11:16:23. 238 [11144.11352] 2 write_blocks: [3616] writing 3968 data blocks of 512 11:16:23.300 [11144.11352] 2 write_blocks: [3616] writing 6272 data blocks of 512
TECH227068 | 2014-12-12
Technical Solutions | CMS-XML

rman-10038 error when attempting to backup Oracle version 11.2 using NetBackup 6.x.

int_startjob()+ 238 call xbsa_validatefeatur 2b0953803000 ? 7fffc2cfcbe0 ?
TECH77071 | 2014-03-14
Technical Solutions | CMS-XML

GENERAL ERROR: ltid hangs on media server. Many oprd processes found running on media server.

19:55:09.240 [15163] 4 QueueMsg: Data.Pid=15185, Type=92, param1=14, param2=30, LongParam=15163 19:55:56. 238 [15163] 2 WaitSocketReady: Processing HOT cmd, Type=100 19:55:56.239 [15163] 4 LtidProcCmd: Pid=4398, Data.Pid=4398, Type=100, param1= , param2=-257, LongParam=-2130640640
TECH56642 | 2013-08-29
Technical Solutions | CMS-XML

Backup of Enterprise Vault(EV) databases, where EV and SQL servers are clustered may fail with Status 72 and Status 1542

Error seen in bpfis: 11:23:57. 238 [7176.6300] 2 onlfi_vfms_logf: INF - fs_fshevbase::SetSQLBECDefualtOpts - entering. 11:23:57.238 [7176.6300] 2 onlfi_vfms_logf: INF - fs_fshevbase::SetSQLBECDefualtOpts - exiting.
TECH204301 | 2013-07-15
Technical Solutions | CMS-XML

Synthetic full backups failing with status code: 671

When the expected incremental component backups are not found, the result of this failure is the status 238 seen in the bpsynth log, and the eventual job failure status 671. SOLUTION:
TECH136270 | 2013-05-02
Technical Solutions | CMS-XML

GENERAL ERROR: A NetBackup synthetic full backup fails with Status Code 671; query for list of component images failed.

08:30:13.578 [1648.3612] 2 synthesize_client_images: synthetics backups matching criteria = 0 08:30:13.578 [1648.3612] 2 bpdbm: request complete: exit status 238 the database contains conflicting or erroneous entries Corrective Action
TECH67048 | 2013-05-02
Technical Solutions | CMS-XML

Application backups fails with status 6 or status 42 when extjob.exe inherits NetBackup sockets

19:22:17.769 [4888] 2 sbterror: INF - leaving ...snip... 19:22:27. 238 [4892] 4 VxBSATerminate: INF - entering VxBSATerminate.
TECH189853 | 2013-03-27
Technical Solutions | CMS-XML

ALL jobs fail with error 237 before any action or resource allocation.

04:31:23.453 [7500] 2 db_class_ex: db_end_sts() failed: the database contains conflicting or erroneous entries 04:31:23.453 [7500] 16 alterinfo: db_setclass_info failed: the database contains conflicting or erroneous entries ( 238 ) BPBRM Log:
TECH137984 | 2010-08-21
Technical Solutions | CMS-XML

VmWare Restore failed with NBU VMware policy restore error (2820) | Symantec Connect

13:07:57. 238 [1320.2068] vddkLog: VixDiskLibVim: VixDiskLibVimLogout
Connect Forums | HTML

getting status code 23: socket read failed.. | Symantec Connect

getting status code 23: socket read failed.. 15:00:46.165 [24993] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.532: vn_request_connect_forward_socket: 10 0x0000000a 15:00:46. 238 [24993] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.549: ipc_string: 2617 15:00:46.240 [24993] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.560: hash_str1: 6e7f6af4e24bd19108d0565492d9cd38
Connect Forums | HTML

Backup failing with error code 23 | Symantec Connect

04:06:34.195 [11370] <2> bpcd main: Not using VxSS authentication with usnbub5500 04:06:34. 238 [11370] <2> bpcd main: bpcd_peername_rqst 04:06:34.238 [11370] <2> bpcd peer_hostname: Connection from host usnbub5500 (171.74.74.1) port 37523
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?