return false; After making this change open SBM System Administrator and click File | Put Files Into Database so your changes will persist after a restart of SBM. NOTE: This change may also need to be redone after an upgrade depending on when this defect gets addressed.
This is erroneous. The Admin will eventually complete (or error). If you stop the process during the upgrade, you must start again with a fresh copy of your database .
Script changes which update the TS_USERSETTINGS table are successfully updated in the database and the table affected is not cached but the change is not immediate in the user workspace. The changes made do not take affect until the web server is restarted .
DMAPPSRV 2011/05/05 08:51:40 E P2064 T5576 DBI0004527E DBIO: Database I/O error occurred ... Error: Unable to connect to database " DMAPPSRV 2011/05/05 08:51:40 E P2064 T5576 Pcms error: 0, Error: Unable to connect to database " ... database =@<SID> After commenting this line out and restarting Dimensions the messages were gone.
Generally, Dimensions CM uses database date format, i.e. date that is set on Oracle for most operations. ... To use the correct format, modify the files to match the database . ... Change the above to suit your environment. 5. After modifying, a stop/ restart of all Services will be needed. Make sure that there are no rogue processes before restarting .
... MSSQL SBM sample database : ... of the SBM database ... to the SBM database . ... If your SBM database is not returned ... DB _NAME( ... ... > 0 and DB _NAME( ... ALTER DATABASE sample SET OFFLINE WITH ROLLBACK IMMEDIATE ALTER DATABASE sample SET ONLINE Apply the following sql statement: ALTER DATABASE sample ... ALTER DATABASE sample SET READ_COMMITTED_SNAPSHOT ON WITH NO_WAIT ... Where <SBM_DATABASE_NAME> is the name of the SBM database In SBM Configurator, restart the Serena Common JBOSS and IIS services.
Workaround:Please use with caution as requires a JBOSS restart and until all Process Apps are deployed successfully orchestrations with event maps will not be working. (1) Take a backup of your Orchestration Engine database ... (3) Restart JBOSS
