opscenter 7.7.3 errors in server log and data collection failure

[Slartybardfast]

Good morning forum,

I have taken over the Netbackup Admin role at work and have had a bit of a baptism by fire. I have upgraded from version 7.5 to 7.7.3 and moved to a new hardware platform. So I am not sure if these errors have alway been there. In the Opscenter gui the two master servers listed are showing the partially connected icon. Looking in the the server log I have the following errors:

2,58330,148,148,107020,1485852215104,5040,264404,0:,3198:DriveCollector7x mastersrv001 ID 800 initialSync failed  - com.symantec.nbu.dbaccess.exception.DbFieldException: OpsCenterDb Column value issue around:domain_TapeDrive(800:HP.ULTRIUM2-SCSI.000) while executing DBAddInsert

2,58330,148,148,107027,1485852222151,5040,264491,0:,1426:PolicyAgent7x mastersrv020 getVMProxyServerList failed - com.Symantec.v70.NetBackup.SL.NBSLOpException: IDL:Symantec/NetBackup/SL/NBSLOpException:1.0

2,58330,148,148,107029,1485852222151,5040,264491,0:,138:PolicyAgent7x mastersrv020 DefaultExceptionHandler handleException NBSLOpException message : ErrorCode - 25 : cannot connect on socket (),2,(0|)

2,58330,148,148,107031,1485852222151,5040,264491,0:,1839:VirtualMachineCollector mastersrv020 failed to retrieve data for virtual machine mediasrv021.another.com- com.symantec.nbu.nom.scl.common.agent.exception.AgentException: ErrorCode - 25 : cannot connect on socket

2,58330,148,148,107036,1485852241823,5040,264491,0:,2369:VirtualMachineCollector mastersrv020 sync failed  - com.symantec.nbu.nom.scl.common.CollectionFailedException: [Nbsl/Agent communication exception]: Data collection failed for proxy server : mediasrv021.another.com

I have tried searching the net and forums but have come to a bit of a dead end. Your guidance would be greatly appreciated.

[Deeps · Accepted solution]

What is the version of Opscenter server  ? I have been to a similar situation . Please try the following steps :

1. Stop the OpsCenter server and webserver services.
2. Make a backup copy of the OpsCenter database
3. Connect to the database with dbisqlc.
4. Execute the following commands in dbisqlc:
   SET OPTION PUBLIC.string_rtruncation = 'OFF';
   commit;
5. Start OpsCenter server and webserver services
6. Collect data and confirm problem resolution.

OR you may use loadsql.bat comand to execute the same command .

Add the commands shown under step 4 above to a text file in a temporary location and then use the loadSql.bat (or loadsql.sh) command to invoke the changes.

Windows:  \Program Files\Symantec\OpsCenter\server\bin\loadSql.bat \temp\filename.txt

UNIX:  /opt/SYMCOpsCenterServer/bin/loadsql.sh -sqlFile /tmp/filename.txt

DeepS

[Slartybardfast]

Hi Deeps

Many thanks for your input. Just curious what does this command do and what is the default setting.

Kind Regards

[Slartybardfast]

Hi DeepS

Many thanks your fix worked a treat on the "DBAddInsert" error in the logs. The server has been connected now for 24 hours plus. I think the other error is down to VMWare access. When I try to browse clients in one of the policies it fails with unable to connect error (25). So i will accept your solution. Many thanks I would have never of got to that resolution in a million years.

[Deeps]

This could happen if the Job Attributes of any job is in big size to fit into column of tables having issue.if you set the string truncation to off in OC db using dbisqlc ,this would cause the string to silently truncate and not cause/raise any db truncation error).

DeepS