Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Promote failed with error "Could not commit JPA transaction"
Promote failed with error " Could not commit JPA transaction "
CMS-XML Error: SQL SERVER "UNABLE TO WRITE CHECKPOINT RECORD" WHEN TRYING TO DUMP TRANSACTION LOG
This usually means the amount of space allocated for the database is full and the dump command can't write the checkpoint record. Have the user run the ALTERDATABASE command to expand the size allocated for the database. The syntax for the ALTERDATABASE command is in the TRANSACT SQL Reference Guide supplied by Microsoft or through the on-line help.
CMS-XML Unable to run or save queries in Web Client where the username contains a backslash
"Fail to get preview Transaction id: 1 Status: 500
CMS-XML 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.
CMS-XML 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.
CMS-XML Error: The currently active transaction was committed before changing the auto commit connection option.
the auto- commit connection option.
CMS-XML 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.
CMS-XML 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'.
CMS-XML What is the new ESPE transaction?
The ESPE transaction replaced the DFHPEP exit. It obtains the CICS 3270 screen image and takes all of the diagnostics gathered at abend time, then formats and writes a WRK record containing those diagnostics.
CMS-XML 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.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs