| |
Results |
|
Dim12: Failed to connect to the Dimensions server - ACL4502922E Error: Cannot open connection to host HOSTNAME - DBI0004527E DBIO: Database I/O error occurred ORA-28000: the account is locked
|
DMAPPSRV 2014/05/06 16:26:26 I P3396 T3400 Connecting to cm_typical@DIM12 DMAPPSRV 2014/05/06 16:26:26 E P3396 T3400 Pcms error: 0, Error: Unable to connect to database "cm_typical" DMAPPSRV 2014/05/06 16:26:26 E P3396 T3400 DBI0004527E DBIO: Database I/O error occurred
|
|
|
|
Dim: Dimensions cannot connect to Oracle database. user gets error ORA-28000: the account is locked
|
If this is the case, rename the file $DM_ROOT/dfs/registry.dat to something like registry.old. Then use dmpasswd < basedb>@<oracle-sid > -add to add the password for each base database and potentially the dmsys user as well. Replace <basedb> with the names of your base databases and <oracle-sid> is replaced with the Oracle SID or Oracle Service Name in use for each database that this Dimensions server will access.
|
|
|
|
KM-DIM-CM2009R2: Description of -restricted_mode parameter in listener.dat
|
The restricted mode parameter in the listener.dat file allows the running of a Dimensions CM listener as a non-root user. This might be desired if root is a locked down account and Dimensions should be run as another user , usually dmsys .
|
|
|
|
DIM2009: RUR returns error PCM0005670E if -user is not dmsys
|
Now change - user to any other local administrator account on the Windows server and restart the listener. Re-run the user defined report
|
|
|
|
Dim12: Deploy: MDHNET4502541E Error: Unable to insert deployment lock for database
|
When reviewing the deployment logs, the following is occurring: 2012/05/29 21:45:41 UTC 0.001 T T3316 DDeployServerAppImpl::dumpConfig: Database[0] = { dmsys , <*****>, MYSERVER, CM_TYPICAL@DIM12} 2012/05/29 21:45:41 UTC 0.015 T T3316 DDeployServerAppImpl::waitForHandshake: Waiting for parent process handshake to complete.
|
|
|
|
Dim10: Deploy on Novell drive does not work - Getting the following error: FSY32000001E Error: Cannot get details of directory F:
|
In addition to the domain\ dmsys user having the drive mapped, the drive also needs to be mapped to the nt authority\system account . The deployment area can now be created in the admin console. Files can now be deployed to the drive and the the post deploy scripts now run correctly.
|
|
|
|
KM-Dim10: Reported Defect DEF108845: User account id is case sensitive on Build Admin checkout
|
Steps to reproduce: Log in as user ‘ DMSYS ’ rather than user ‘ dmsys ’ into the Admin Console. If you ‘check out’ a build configuration for modification and terminate the session before completing the modification.
|
|
|
|
KM-Dim9: Documentation on user roles, $roles, allowed role functions - Explained role functions to client
|
First of all roles preceded with the '$' are special roles that are assigned when a product is created. They should be assigned to the DMSYS account which is the $TOOL-MANAGER. Generally, these roles cannot be reassigned once created, therefore we recommend that they always be assigned to the DMSYS account.
|
|
|
|
KM-Dim7: Error: PCMS Library does not exist.
|
Once the permissions were change, DFS stopped and restarted (using the root account ) the users were able to create and work with items.
|
|
|
|
Dim: Locked Workset not shown as locked via DMCLI
|
The Work Set default Design Part is not defined The current user is DMSYS Description : Temporary Load Workset
|
|
|
