![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
ERROR - Bad update enable string 'Yes' ERROR - No parameters downloaded
After installing the fix the parameter values can be written in any of the following ways: "YES", "Yes", "yes", "NO", "No", "no".
errors.com.ibm.it.rome.slm.runtime.data.AgentHandler ERROR COM.ibm.db2.jdbc.DB2Exception: IBM CLI Driver DB2/6000 SQL0433N Value "Windows NT 5.0 - Service Pack 4, RC 4.66" is too long. SQLSTATE=22001This is because in the runtime server database, the AGENT table field for the operating system was too small.
After applying the fix the database table field (AGENT.OS_VERSION) is increased to 60 characters, and the problem does not occur.
After you have installed the fix, the runtime server will allow a thread to wait for a maximum of 60 seconds for a requested resource to be made available. If the request cannot be satisifed within this period, an event of type "internal error" is sent to the agent. The agent has processes for handling such an event, and the load on the runtime server and HTTP server is lightened.
10-03-10.55.29 {Communication#142} com.ibm.it.rome.slm.scp.ServiceHandler [ERROR] java.lang.NumberFormatException: null at java.lang.Long.parseLong(Long.java(Compiled Code)) at java.lang.Long.parseLong(Long.java(Compiled Code)
After installing the patch these Java exceptions are handled correctly.
After installing this fix you will be able to choose the time of day when all these services start. The installation of the fix will add a new parameter: runtimeBaseTime to the system.properties file on the runtime server. The default value of this parameter is 23:00 (11 pm), according to the clock of the runtime server. After you have installed the fix, the service requests will be made according to this parameter, and each will be satisfied in turn. The existing individual frequency parameters will then determine when the service is next run. Thus, for example, if the frequency interval of a service is 1440 minutes (24 hours), and you leave the runtimeBaseTime at its default value, the service will start at 23:00 (11 pm) every day. The server uses the runtimeBaseTime parameter only immediately after it has started; from that point on it will determine the next service start by adding the appropriate frequency to the time of the previous service start.
In conjunction with this, after installing the fix, the following parameters in the system.properties file on the runtime server have new default values, different from those documented in the IBM Tivoli License Manager: System Administrator's Guide:
# Time interval for internal inventory update (minutes) inventoryUpdatePeriod=1440 # Time interval for internal cache update (minutes) cacheUpdatePeriod=1440 # Time interval for data transfer (download) with admin server (minutes) adminDownloadPeriod=1440 # Time interval for data transfer (upload) with admin server (minutes) adminUploadPeriod=1440 # Time interval for license cleanup checking (minutes) licenseCleanupPeriod=1440 # Time interval for usage data resynch with admin server (minutes) usageSnapshotPeriod=1440
[ Top of Page | Previous Page | Next Page | Contents ]