| |
Results |
|
Unable to run or save queries in Web Client where the username contains a backslash
|
"Fail to get preview Transaction id: 1 Status: 500
|
|
|
|
Errors in ns.log when using User Channel (console-plugin-1.1.jar) for Notification Monitoring and logging in ns.log. ERROR: Write operations are not allowed in read-only mode
|
org.springframework.dao.InvalidDataAccessApiUsageException: Write operations are not allowed in read-only mode (FlushMode.MANUAL): Turn your Session into FlushMode. COMMIT /AUTO or remove 'readOnly' marker from transaction definition.
|
|
|
|
No log record written when install fails in CMN21 rather than CMN20
|
We changed install job CMN21 bind failure to work like CMN20I install failure. On an "ALL" site, failure executes CMNBATCH transaction 99 with FUN=21 at the "ALL" site. This transaction notifies the package creator of the bind failure.
|
|
|
|
Work center deploy/promote failed if search settings option is defined
|
Could not commit JPA transaction ; nested exception is javax.persistence.RollbackException: Transaction marked as rollbackOnly
|
|
|
|
Long name transactions not being logged for forward recovery
|
The use of long name components (greater than 8 characters) is not writing recovery records to CMNELLOG. In the event of a restore of the component master using forward recovery, the long name component activity is not restored.
|
|
|
|
Errors in ns.log - An error occurred while adding an event to the Events table ... Nested exception: org.springframework.dao.DataIntegrityViolationException: could not insert ... Caused by: org.hibernate.exception.ConstraintViolationException ... Violatio
|
.impl.SessionImpl.managedFlush(SessionImpl.java:365) at org.hibernate. transaction .JDBCTransaction. commit (JDBCTransaction.java:137) at org.springframework.orm.hibernate3.HibernateTransactionManager.doCommit(HibernateTransactionManager.java:656) ... 14 more Caused by: java.sql.SQLException: Violation of UNIQUE KEY constraint 'TC_UNIQUE_NOTIFICATIONEVENTS '. Cannot insert duplicate key in object 'dbo.TS_NOTIFICATIONEVENTS'.
|
|
|
|
S0C7 abend occurs in SERDATES at OFFSET 222, when CMNDELAY processes "CMNDELAY - ****000000 95 AGEI" transaction.
|
If the housekeeping job is run while the ZMF task is down, so that the transaction are written to the delay file and processed by CMNDELAY when the task is brought up, the following S0C7 abend occurs, if all applications (****920=Y for SYSIN) are processed. If only 1 application is processed the abend does not occur.
|
|
|
|
Transaction was deadlocked... during concurrency actions: Copy Dimension and modifying of Financial Details.
|
2. User B. Select "ROI Network Management PR" and open "Financial Details". Select Capex\Others. Change a existing value in bottom pane but NOT press Save button.
|
|
|
|
Unexplained message/CMNBATCH type 95 transaction produced during housekeeping
|
This is related to but not identical to the problems documented under DEF92801/DEF170355. They are dealing with the potential impact of these transactions being written to the delay file.
|
|
|
|
CMNBATCH and CMNDELAY fail to update calendar and incorrect message is issued.
|
When CMN930 transactions are processed by CMNBATCH the following CMNVRLIO messages are written to the SERPRINT dd in the task and the calendar is not updated: If task is down when CMNBATCH runs, the following are issued when CMNDELAY processes the records. CMNE464I CMNVRLIO VCA=0B6A9000,USER=SERVDLAY,Active Lock..: ....0000000000000000,TTOK=00000000
|
|
|
