Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML DimCM: 14.4: Upgrade: SQL Server: Upgrade cannot proceed when other users are connected to schema
Workaround: Stop both Server 1 and Server 2 services/processes so that neither are connected to the database. Then log into DMDBA similar to the following and run the upgrade command:
CMS-XML KM-Dim9: Unable to login or connect to base database after 9.1.3 upgrade
After upgrading to Dimensions 9.1.3 users are unable to login to Dimensions. OR After upgrading to Dimensions 9.1.3 the Dimensions Listener process keeps stopping.
CMS-XML Minimum privileges required for the Oracle user connecting to an SBM schema
The following privileges are required for creating a new SBM database or upgrading an existing one. Caution:
CMS-XML Dim CM 12.2: Unable to connect to specific base database following upgrade to 12.1
In order to solve this we needed the user to generate SDP trace files by setting DM_SDP_TRACE in dm.cfg and restart the Serena Dimensions Listener. Having received a complete set of SDP logs the following was visible at the end of one of the DMAPPSRV traces:
CMS-XML KM-Dim10: Unable to connect to basedb after upgrade to 10.1.1 - basedb password not default
file. Now run the dmpasswd command for the Dimensions user (usually dmsys or the value specified in the listener.dat file for parameter -user):
CMS-XML KM-Dim9: After upgrade to Dimensions, Desktop Client connection is getting errors: "Incompatible Schema "
To determine if the account that has been used for the upgrade (or will be used if the upgrade has not yet been attempted) has an OPS$<username> user the following test may be used. Log into the account in question, and type "sqlplus /" at a DOS prompt or Unix shell prompt. If sqlplus connects to the database without requiring a password then then an OPS$<username> account exists for this user .
CMS-XML DimCM: Upgrade: DBI4502373E [Microsoft][SQL Server Native Client 11.0][SQL Server]The specified schema name "SCHEMANAME" either does not exist or you do not have permission to use it
2. Now run the following commands: connect pcms_sys select * from pcms_sys.pcms_seq where basedb = 'INTERMEDIATE';
CMS-XML Dim CM 14.x: Unique constraint violations on VRS_1_A_F1 and/or VRS_2_P_PK during schema or VRS upgrades
SQL> purge recyclebin To disable the recycle bin as the user connected with sysdba privilege you need to run: SQL> alter system set recyclebin = OFF SCOPE = SPFILE;
CMS-XML ResMan server schema failed during upgrade of Common Services, but no error was logged during the upgrade
After the upgrade is complete and you try to log into work center, users will see "Unable to validate user , please contact your Administrator" and errors such as the following will be in different logs. However it is very difficult to resolve the problem based solely on these errors.
CMS-XML External users and/or users without the View Privilege on the Contact table cannot search Relational Field Value Lookup forms for single relational fields
Having upgraded the DB from TT6.3 to TT 6.6 External users and/or users without the View Privilege on the Contact table cannot search Relational Field Value Lookup forms for single relational fields on Submit transitions. The lookup search brings nothing at all, neither an error nor a result.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs