Technical Blog Post
Abstract
WPA reports SQLSTATE=22525.
Body
WPA reports SQLSTATE=22525.
The error message in the WPA logs is:
SQLException: Error for batch element #728: DB2 SQL Error: SQLCODE=-327, SQLSTATE=22525, SQLERRMC=ITMUSER.NT_Server, DRIVER=4.17.29
== 5150825 t=Thread-240 SQLState: 22525
== 5150826 t=Thread-240 Message: Error for batch element #728: DB2 SQL Error: SQLCODE=-327, SQLSTATE=22525, SQLERRMC=ITMUSER.NT_Server, DRIVER=4.17.29
== 5150827 t=Thread-240 Error Code: -327
this is reported when the WPA tries to input data into the warehouse. In this case the data is for th NT_server but it could be for any attribute.
The error message SQLCODE=-327, SQLSTATE=22525 means:
"The row cannot be inserted into table <table-name> because it is outside the bounds of the defined data partition ranges."
The warehouse database can be set up to use partitioning, which can help performance.
However if this is done it must be set to yes in the config files for both the WPA and the S&P agent.
For more details on setting this up there is a section in the Installation Manual:
The value set to Y in the WPA configuration, means that the warehouse proxy agent will check for the correct partition to put data into.
The value set to Y in the S&P agent means it will create the partitions.
Only the Summarization and Pruning Agent manages the addition to, and deletion of (or rotation of), partitions from a table.
If the above error is seen, the first area to check is if this has been working correctly and the values are still set in both config files.
Then check if there has been any outages for the S&P agent. If this agent has not been running, or has had errors the partitions may not have been created for the new data.
If it is a case that the S&P agent has not been running, fix the issue with it, or just start it (if there hasn't been an error).
Once the S&P agent has run through its first full run (if it has been down this may take a while) the partitions will be created and the WPA should be able
to input the data. The WPA will automatically keep trying to send the data, so nothing needs to be done to set this in motion.
The WPA logs will need to be checked again for errors, or of course you may now be able to see historical data that was not available.
Subscribe and follow us for all the latest information directly on your social feeds:
|
|
![]() |
|
| Check out all our other posts and updates: | |
| Academy Blogs: | https://goo.gl/U7cYYY |
| Academy Videos: | https://goo.gl/TLfMoF |
| Academy Google+: | https://goo.gl/HnTs0w |
| Academy Twitter : | https://goo.gl/HnTs0w |
UID
ibm11278190




