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 Dim CM 2009 R2: Trigger records semaphore lock and fails in certain instances
When using a trigger there are certain instances where the trigger fails . These situations, along with how to recreate them, are described below: -
CMS-XML KM-Dim9:9506-DB_FAILED_TABLE_LOCK  Failed to lock table %s for update
KM-Dim9:9506-DB_FAILED_TABLE_ LOCK Failed to lock table %s for update
CMS-XML 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
Logging into Dimensions, the following error message is returned: Failed to connect to the Dimensions server. ACL4502922E Error: Cannot open connection to host HOSTNAME
CMS-XML Dim12.x: Deployment: Unable connect to database + Failed to lock database + Failed to connect to database
2013/02/11 08:53:58 UTC 1.052 T T885561088 DDeployService::connectToDb: Connecting to database < dbname@sid > on host ... as user <userid>... 2013/02/11 09:03:00 UTC 542.379 T T885561088 DDeployServiceLockImpl::acquire: Error: Unable connect to database < dbname@sid > on host ... in order to lock it.
CMS-XML Dim12: Deploy: Deploy server fails when starting with this error "Error: Unable connect to database @ on host in order to lock it."
DDeployService::connectToDb: Connecting to database <dbname>@<sid> on host <hostname> local as user dmsys ... DDeployServiceLockImpl::acquire: Error: Unable connect to database <dbname>@<sid> on host <hostname> in order to lock it. DDeployServiceLockImpl::acquire: Failed to lock database <dbname>@<sid> on host <hostname>.
CMS-XML Dim cm 14.4: not possible to login to pulse, getting error "Could not acquire change log lock. Currently locked by () since "
login to pulse fails and returns this message: "Could not acquire change log lock . Currently locked by <user> (<user ip address>) since <date>
CMS-XML 2009R2 : when locking a project (LCK) from Jenkins, got the error : "PCM4300038E Error: This command cannot be used in the current"
Here the error when trying to lock a project from jenkins : [DIMENSIONS] 2551 fetch operations succeeded, 0 failed . [DIMENSIONS] Getting files: 13.556883 sec
CMS-XML Dim: Dimensions cannot connect to Oracle database. user gets error ORA-28000: the account is locked
If a user has updated the Oracle password for a Dimensions base database and then the user mistypes the password into the dmpasswd utility, thus registering an incorrect password this can happen. The Dimensions processes running will attempt to connect using the incorrect password and some of these processes will retry on error. Depending on the Oracle account profile in use, the number of failed attempts may be quickly exceeded and Oracle locks the account.
CMS-XML Dim12: Deploy: MDHNET4502541E Error: Unable to insert deployment lock for database
2012/05/29 21:45:42 UTC 1.016 T T3560 DDeployService::connectToDb: Connecting to database CM_TYPICAL@DIM12 on host MYSERVER as user dmsys ... 2012/05/29 21:45:48 UTC 6.909 T T3560 DDeployServiceLockImpl::dbInsertDeploymentLock: Caught a DbException: MDHNET4502287E Error: Failed to execute a statement.
CMS-XML 12.2.x : deploying 3000 items in a area causes deploy server to hang and lock deployment in others areas. Is there one single deployment jobs queue for all areas or a jobs queue per area ?
There is a single queue for all jobs, but the areas are locked independently. If one area is blocked due to a failed transaction it should not affect another area that was not involved in that transaction. However there is another issue that WILL cause this to happen.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs