| |
Results |
|
Mariner Administrator gives error "Logon Failed: Could not get database version information" after upgrade
|
Mariner Administrator gives error "Logon Failed: Could not get database version information" after upgrade
|
|
|
|
KM-Dim8: Error Schema version check failed for Dimensions database "DMSYS" Communications error has occurred
|
KM-Dim8: Error Schema version check failed for Dimensions database "DMSYS" Communications error has occurred
|
|
|
|
After upgrade Composer fails to validate if table database name >24 characters. Worked in previous version.
|
After upgrade Composer fails to validate if table database name >24 characters. Worked in previous version.
|
|
|
|
Process the 10.x notification server uses to configure the database from a previous version of SBM/TT
|
1. NS checks if the schema exists, by checking existence of the NS_REGISTRY table (contained in the database JBOSS is connected to). In case of 2009R2 this table doesn’t exist, thus schema is considered absent in DB.
|
|
|
|
SBM 10.x database upgrade to SBM 11.x gives error "Failed to get Application Engine version" and "Couldn't get applications count"
|
When you upgrade to SBM 11.0+, part of the process is to upgrade the Orchestration Engine database . (See KB S142694 for details.) In this document, we will talk about the failure caused by this error:
|
|
|
|
12.2.x : when doing a fresh installation of server, got the error "A version of Dimensions CM has already been install into this database"
|
user starts a fresh installation of server + schemas.The database is located on a remote Oracle server and an oracle client has already been installed on the machine where the Dimensions server is going to be installed. After selecting the demo schema to install in the installation procedure , he gets the error : "A version of Dimensions CM has already been install into this database ..."
|
|
|
|
How to verify the version of the ChangeMan database
|
* Please note if the server version and the database version are not the same, potential problems will occur.
|
|
|
|
VM: Basics: What database is used by Version Manager for storing information about various versioned files/archives?
|
files are mostly 'serialization' files (with an extension of '.ser') that store information about Project Database's projects, sub-projects, workspaces and users. The '.ser' file type is mostly used by Java applications, indicating files that contain serialized Java objects. The internal format of these files is dependent on the specific Java classes used by VM to store its data.
|
|
|
|
Can COMPAREX compare an active database with an archived (image copy) version?
|
'This has been requested before. Many years ago I wrote COMPAREX to unload any database to a flat format. Regression testing demanded that testers go back to a precise point in time to compare against.
|
|
|
|
Dim12: ACL4502922E Error: Cannot open connection to host HOSTNAME Error: Dimensions database "cm_typical" has incompatible schema version
|
DMAPPSRV 2014/06/02 14:52:34 E P1196 T3636 Error: Dimensions database "cm_typical" has incompatible schema version 10.1.2 (required schema version is at least 12.x) DMAPPSRV 2014/06/02 14:52:34 E P1196 T3636 Pcms error: 0, Error: Unable to connect to database "cm_typical"
|
|
|
