IC96010: SCANS ON FILESYSTEMS MAY FAIL OR PROBE DATA CANNOT BE SENT TO DATA SERVER. FAILING WITH ERROR CODE AGT0306E. NON-ASCII CHARS

Fixes are available

APAR status

Closed as program error.

Error description

There are two sets of behavior seen with this APAR.  One for the
probe and one for the scan.

#1 - Successful probe but then errors seen

The probe result fails to reach the Data Server because some of
the probed directory name contain Japanesse chars(Unicode char)
that cannot be parsed by the DataServer.
SRA probe code that supports only ASCII chars and not Unicode.
Below is the message logged in agent.log

07/06/2013 20:29:27 AGT0301I Extracting agent.zip ...
07/06/2013 20:29:27 AGT0301I Extracting probe.zip ...
07/06/2013 20:29:27 AGT0301I Extracting certs.zip ...
07/06/2013 20:29:27 AGT0279I Registry entry added for
installation location C:\Tivoli\TPC_SRA
07/06/2013 20:29:27 AGT0281I Config file entry added for server
onstpc01.smsjapan.local, and port number 9549
07/06/2013 20:29:28 AGT0404I Creating Common Agent Package file
C:\ProgramData\Application Data\IBM\CAP\sra1_default.tmp...
07/06/2013 20:29:28 AGT0406I Common Agent Package file
C:\ProgramData\Application Data\IBM\CAP\sra1_default.tmp
created.
07/06/2013 20:30:20 AGT0305I Successfully sent Agent,
C:\Tivoli\TPC_SRA, registration to server
onstpc01.smsjapan.local
07/06/2013 20:30:26 AGT0306E Failed to send Probe complete
status to server, C:\Tivoli\TPC_SRA


#2 - Scans on files systems may fail if name contains non-ASCII
characters

The following messages can be found in the SRA Scan log:
STA0161I Sending scan results to server.
STA0022E Server did not accept scan results
STA0028I Scan aborted

In the Data Server logs ( TPC/data/log/TPCD*.log ) on TPC server
we can find the following messages:

10/22/14 7:28:35 PM STS0146E: Last prepared INSERT SQL
statement:
insert into t_stat_file (filesystem_id, statistic_id,
statistic_type, logical_s\
ize, physical_size, path, name, owner_id, group_id,
creation_time, access_time\
, modification_time, attributes) values
(?,?,?,?,?,?,?,?,?,?,?,?,?)
com.ibm.db2.jcc.am.co: DB2 SQL Error: SQLCODE=-302,
SQLSTATE=22001, SQLERRMC=null, DRIVER=3.57.82
   at com.ibm.db2.jcc.am.bd.a(bd.java:668)
   at com.ibm.db2.jcc.am.bd.a(bd.java:60)
   at com.ibm.db2.jcc.am.bd.a(bd.java:127)
   at com.ibm.db2.jcc.am.km.b(km.java:2164)
   at com.ibm.db2.jcc.am.km.c(km.java:2147)
   at com.ibm.db2.jcc.t4.db.k(db.java:354)
   at com.ibm.db2.jcc.t4.db.a(db.java:60)
   at com.ibm.db2.jcc.t4.t.a(t.java:50)
   at com.ibm.db2.jcc.t4.tb.b(tb.java:218)
   at com.ibm.db2.jcc.am.lm.ec(lm.java:2692)
   at com.ibm.db2.jcc.am.lm.b(lm.java:3552)
   at com.ibm.db2.jcc.am.lm.b(lm.java:3697)
   at com.ibm.db2.jcc.am.lm.Wb(lm.java:690)
   at com.ibm.db2.jcc.am.lm.executeUpdate(lm.java:673)
   at
com.tivoli.itsrm.repository.RepositoryAccessor.executeUpdate(Rep
ositoryAccessor.java:290)
   at
com.tivoli.itsrm.TStorm.repository.TStatFile.insertOnly(TStatFil
e.java:206)
   at
com.tivoli.itsrm.TStorm.server.svp.ScanResultsHndlr.processCuSta
tResults(ScanResultsHndlr.java:2792)
   at
com.tivoli.itsrm.TStorm.server.svp.ScanResultsHndlr.processResul
tsByFS(ScanResultsHndlr.java:2889)
   at
com.tivoli.itsrm.TStorm.server.svp.ScanResultsHndlr.processCuSta
tDef(ScanResultsHndlr.java:2462)
   at
com.tivoli.itsrm.TStorm.server.svp.ScanResultsHndlr.handleSRA(Sc
anResultsHndlr.java:2242)
   at
com.tivoli.itsrm.TStorm.server.svp.ScanResultsHndlr.handle(ScanR
esultsHndlr.java:455)
   at
com.tivoli.itsrm.server.RequestManager$RmThread.run(RequestManag
er.java:499)
10/22/14 7:28:35 PM GEN0100E: Error processing request from host
<my.tpc.agent.machine>,
                         for service <Agent>, request(4, 2)
10/22/14 7:28:35 PM GEN0133E: Error reading file {0}

Local fix

```
Contact Support for workaround
```

Problem summary

****************************************************************
* USERS AFFECTED:                                              *
* TPC 5.1.x and 5.2.0 users with Storage Resource Agents using *
* a double-byte  character language such as Japanese.          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See ERROR DESCRIPTION.                                       *
****************************************************************
* RECOMMENDATION:                                              *
* Apply fix maintenance when available.                        *
****************************************************************

Problem conclusion

The fix for this APAR is targeted for the following maintenance
package:

| fix pack | 5.1.1-TIV-TPC-FP0002
| refresh pack | 5.2-TIV-TPC-RP0001 - target March 2014

http://www-01.ibm.com/support/docview.wss?&uid=swg21320822

The target dates for future fix packs do not represent a formal
commitment by IBM. The dates are subject to change without
notice.

Temporary fix

Comments

APAR Information

APAR number
IC96010
Reported component name
TPC
Reported component ID
5608TPC00
Reported release
511
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-09-17
Closed date
2013-09-19
Last modified date
2015-02-04

APAR is sysrouted FROM one or more of the following:

IC94655
APAR is sysrouted TO one or more of the following:

Modules/Macros

```
SRA
```

Fix information

Fixed component name
TPC
Fixed component ID
5608TPC00

Applicable component levels

R510 PSY
UP
R511 PSY
UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS5R93","label":"IBM Spectrum Control"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"511","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
23 March 2022

Tips

IC96010: SCANS ON FILESYSTEMS MAY FAIL OR PROBE DATA CANNOT BE SENT TO DATA SERVER. FAILING WITH ERROR CODE AGT0306E. NON-ASCII CHARS

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R510 PSY

R511 PSY

Document Information

Share your feedback

Need support?