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 When you open the Notifications area in your settings while in Work Center you may see an error "No row with the given identifier exists" com.serena.sbm.data.Notification#XXX
When you open the Notifications area in your settings while in Work Center you may see an error " No row with the given identifier exists " com.serena.sbm.data.Notification#XXX
CMS-XML MCLG: When migrate the admin database or project database to Oracle , get error "ORA-06550: line 1, column 7: PLS-00201: identifier 'DBMS_JAVA.GRANT_PERMISSION' must be declared" or "Roll 'Java Admin' does not exist."
MCLG: When migrate the admin database or project database to Oracle , get error "ORA-06550: line 1, column 7: PLS-00201: identifier 'DBMS_JAVA.GRANT_PERMISSION' must be declared" or "Roll 'Java Admin' does not exist ."
CMS-XML Getting ORA-00904 Invalid Identifier, ORA-06512 or ORA-04088 when trying to open up existing documents or creating new ones after upgrading to RM 10.1.3 from RM 10.1.2 and only Oracle 9i is being used (does not happen under Oracle 10g).
Error Code: 904 Message: 904, ORA-00904:"ATTR_xxxx":Invalid identifier ORA-04088: Error during execution of trigger 'the trigger name'
CMS-XML 2nd Import does not update records when using a Unique Identifier of Character
(1) Create a sql table with two columns that hold text e.g. nchar(10), varchar(50). Add a couple of rows with unique data in nchar field .
CMS-XML CreateUser web service should not use Display Name as a Unique Identifier
The same behavior is not followed with the webservice. If the DisplayName is not unique, even if the LoginID is unique, the user will not be created. However, you can create a user with a unique DisplayName via the webservice and go into SBM Administrator and change the DisplayName to one that does exist and it accepts the name.
CMS-XML KM-Dim9: Replicator: Error: Replication configuration does not exist.
Ensure that Replicator is invoked with the correct replication configuration identifier .
CMS-XML KM-Dim9: 2214 Error item identifier is not specified
KM-Dim9: 2214 Error item identifier is not specified
CMS-XML ORA-12154: TNS:could not resolve the connect identifier specified
ORA-12154: TNS: could not resolve the connect identifier specified
CMS-XML SLM vendor daemon cannot use "localhost" as SERVER identifier
SLM vendor daemon cannot use "localhost" as SERVER identifier
CMS-XML Dim12: SQL Server: The multi-part identifier "pcms_seq.nextval" could not be bound
Dim12: SQL Server: The multi-part identifier "pcms_seq.nextval" could not be bound
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs