| |
Results |
|
Intermittent errors when accessing items or listing report - Error: The connection is broken and recovery is not possible
|
The connection is broken and recovery is not possible. The client driver attempted to recover the connection one or more times and all attempts failed. Increase the value of ConnectRetryCount to increase the number of recovery attempts.
|
|
|
|
SBM for Oracle driver does not recover after losing its connection
|
If an Oracle database goes off line (during backups, for example), the SBM server will try to re-establish the connection for about 20 minutes and then fails to try any further. It is expected that SBM will try periodically until the database comes back online, however, this is not the case with the Oracle for SBM Driver / Oracle.
|
|
|
|
Server.log error "Failed to obtain DB connection" and "Connection refused" and "Could not retrieve datasource" and "Destroying connection that could not be successfully matched" and "Connection error occurred" and "Destroying connection that is not valid"
|
If there is a short database connectivity disruption, the SBM UI may recover , and the users may never know that something happened. However, if an orchestration runs and try to make an SBM web service call (for example, to abmappservices72), the web service call will fail and the errors above will be in the server.log. A second SBM web service call will succeed.
|
|
|
|
KM-Dim7: How to recover datafiles in the event of 1018-DBIO: connect failed, ora-01092: oracle instance terminated the disconnection forced. error: unable to connect to database
|
Startup Note: make sure database starts without issuing warnings or errors Lastly, restart Dimensions services and attempt connection .
|
|
|
|
SBM hangs suggest to increase ConnectRetryCount with SQL Server 2014 or later
|
Application event log will have several errors like "The connection is broken and recovery is not possible . The client driver attempted to recover the connection one or more times and all attempts failed. Increase the value of ConnectRetryCount to increase the number of recovery attempts."
|
|
|
|
PCLI repeatedly requests the same license, causing the SLM License Server to (temporarily) fail for all users
|
... circumstances it is possible for PCLI to ... ... OS) can no longer establish a new TCP connection . Network clients of other server processes running on the SLM server system can no longer establish a new connection to the sever, while clients with already established connections remain unaffected. Although the server will normally recover from this event after the PCLI client causing the problem terminates, this can take some time as the TCP sockets that were used need to go through their TIME_WAIT cycle before becoming available again.
|
|
|
|
SBM 10.x database upgrade to SBM 11.x gives error "One or more deployment failures were encountered during the database upgrade process"
|
... we review some possible causes and how to recover from this error ... ... which process app failed and to which ... ... one or more failures . ... have addressed the failures and you want ... If you are not completely sure that ... Common Failure Errors: Cannot deploy BPEL definition ... xxxxxxxxxxxx/ - Could not deploy process ' ... .. Deploy failed ; error: ... Failed to get Application ... Couldn't get applications count for 'ENV NAME' environment due to exception. ... Cannot deploy BPEL definition for process model alf/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/ - Connection refused: connect
|
|
|
SBM Version Diff
|
Differences Between Versions } \ No newline at end ... ... ; } \ No newline at end ... \ No newline at end ... \ No newline at end ... \ No newline at end ... ... = "We could not locate all of ... ... "Sorry, no data was found ... ... | "We could not locate all of ... ... "Sorry, no data was found ... ... that might have no text - var ... ... with backgroundImage and no text ... // if was not already in the ... ... // ignore no label.. ... ... + // does not need unescape from ... ... = null) break ;
|
|
|
|
TeamTrack version 6.6.1.19 build 66159 patch
|
... Group privileges are no longer erroneously removed ... than 5MB no longer occur on Oracle ... ... has expired” no longer failures when making calls ... ... FireFox browser windows no longer automatically No manual changes to ... TeamTrack no longer corrupts existing TeamTrack ... ... the destination database does not have enough free ... ... now honored in connections made to the ... a connection to the TeamTrack ... connection with each new ... ... This change prevents possible server hangs and ... -transition script fails the transition and ... ... Journal field is no longer ignored ... Viewer via TeamScript no longer cause server hangs ... ... Change History is no longer lost when using ...
|
|
|
|
SBM Version Diff
|
Differences Between Versions ... >Reference Name is not unique within the ... however, you do not have the privilege ... ... however, you do not have the privilege ... ... : This report cannot query Perforce actions ... ... ">Items were not included due to ... ... The primary table doesn't contain Submit Date ... ... NOTEMPTY"> is not empty ... NOUSERSINGROUP"> No users in this ... ... scheduled reports changes are not saved.< ... ... report request was failed ... >SUM function is not supported. ... UNDELETE"> Cannot undelete because all ... ... product access types are not available for the ...
|
|
|
