|
Results |
|
Oracle: Error "select statement could not be read from the 'Attachments' table" during database upgrade to TeamTrack 6.6.1
Oracle: Error " select statement could not be read from the 'Attachments' table" during database upgrade to TeamTrack 6.6.1
|
|
|
Unable to read selected item. SQL Statement has possible SQL Injection when using "--" in a query
Unable to read selected item. SQL Statement has possible SQL Injection when using "--" in a query
|
|
|
Dim12: ORA-00376 File 4 cannot be read at this time
eg SQL> recover datafile 4; Run the select statement again and check if the datafile is offline, if so you can put it online with the following. SQL> alter database datafile 4 online;
|
|
|
Cannot associate Version Manager files with Teamtrack 6.6.1.04 Items on Check-in
The record list with the 'select * from TS_VCACTIONS where TS_FILENAME like ? and TS_AUTHOR1=? and TS_ACTIONS2=?' select statement could not be read from the 'VCActuions' table.
|
|
|
Out of Office delegation doesn't work if you rename the Owner field.
TS_ACTIVEINACTIVE, USR_OOO.TS_PROJECTID, USR_OOO.TS_STATE, USR_OOO.TS_OWNER, USR_OOO.TS_LASTMODIFIEDDATE from USR_OOO with (nolock) where TS_PROJECTID=? and TS_NEW_OWNER=?' select statement could not be read from the 'OOO' table.
|
|
|
Deleting a contact from the SBM Administrator tool in the Contacts Auxiliary table you may get the following error in the UI and the contact doesn't get deleted. "An exception occurred while attempting to fetch a record count or a record integer value from the database"
The record list with the 'select .TS_ID, .TS_UUID from with (nolock) where TS_ID in ( select TS_SOURCERECORDID from TS_USAGES where TS_FIELDID=153 and TS_RELATEDRECORDID=7)' select statement could not be read from the '' table.
|
|
|
How To: Example pre-build script to scan for and build .Archive statements for multi-labeled builds
.Archive .c_v(.c $(LABEL)) would not work unless ALL sources contain the $(LABEL) label within one of the revisions in the archive. #script.bld
|
|
|
ChangeMan ZMF DB2 Option Getting Started Guide
2 Delete ddnames CMNIMPFL and CMNBUNFL. These DD statements point to the sequential impact analysis and BUN files, respectively, which are not read when the DB2 Option is licensed.
|
|
|
Serena StarTool FDM 7.3 StarBat Option
4. If the above expansion fails because there is not a previous parameter, StarBat scans for the next comma to the right and splits the JCL statement after that parameter. Again, the new JCL line is indented to match the split JCL line.
|
|
|
ChangeMan ZMF DB2 Option Getting Started Guide
c If no BIND PACKAGE member name or templated BIND PLAN name matches the names returned from the DB2 catalog scans , the name of the DBRM is added to a “bind statement required list”. 4 If the “plans to be bound” list is empty, and control statement NODBRMFOUND is omitted or commented out, CMNDB2PL stops with a RC=12 and the message, NO PLANSHAVEBEENFOUNDTOBIND is printed.
|
|
|