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 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"
select count(1) from where TS_MYSINGLEREL=7 Incorrect syntax near the keyword 'where'. If you open the Event Viewer on the Application Engine server and look in the Application Log you may see the following errors related to this situation.
CMS-XML Schema document for ts_users table incorrect
Schema document for ts_users table incorrect
CMS-XML Using System Administrator tool to import to Aux table get "Killer Import Error: Duplicate destination keys not allowed."
When you use the System Administrator tool to import data from another database or an excel spreadsheet you may see the following error during import.
CMS-XML Purge process terminated due to the following error: Error processing table: java.sql.SQLException: ORA-10635: Invalid segment or tablespace type
This is not a Purge issue per se but because it tries to shrink the tables . You will need to check if or tables are compressed or how your autosegment space is managed.
CMS-XML subquery ERROR -- An exception occurred while attempting to set the initial column string data for column in the table.
The statement has been terminated. An exception occurred while attempting to add the field to the 'Fields' table . [(|TTexcIDS_EXC_ADD_FIELD_TO_TBL|)]
CMS-XML After upgrade to SBM 10.1.3+ orchestration workflow may get error "Invalid item id 0 for table 0."
/ Details Looking at the Common Log after upgrading you may see an error with message of "Invalid item id 0 for table 0." Reviewing the common log and orchestration, it will appear that the field is being passed as expected. This error can be caused by the following situation.
CMS-XML Running Mariner migration tool get this error. ALTER TABLE PES_ObjectAuditCurrent DROP COLUMN aud_Text
Running Mariner migration tool get this error . ALTER TABLE PES_ObjectAuditCurrent DROP COLUMN aud_Text
CMS-XML What's New or Getting Started screen shows error in Agile about Object Not Set to Reference or 404 file or directory not found.
This error can happen if a specific value is missing from the PES_System table or an existing value is no longer valid.
CMS-XML What's New or Getting Started screen shows error in Mariner about Object Not Set to Reference or 404 file or directory not found.
This error can happen if a specific value is missing from the PES_System table or an existing value is no longer valid.
CMS-XML Error: "We're sorry, you cannot submit a new xxxxxxx Request from this popup window. Please use the Submit button on the application bar."
For relational fields (a multi-relational and a single relational field) that point to a primary table to get their values there is an icon next to each of these fields with the text "Click to Create or View the Change Request in a Popup Window". When there isn't an item selected yet and the icon is clicked you get a window that looks like an error. You can view an item if one is already selected, but you cannot create a new record by clicking the icon.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs