Find Answers

Filter Search Results

Ask a Question

Example: "Database could not be verified"

Pages [Next]

Results

Mashups may fail to deploy if they contain auxiliary tables that were deleted

To workaround this problem in the meantime, delete the roles that were associated with deleted auxiliary tables , and then recreate the roles as needed.

Validation fails with "Applications is a reserved table name" when deploying after upgrading to 10.1.5

SBM 10.1.5 brought in a change where we now prevent you from creating or having a table called "Applications" in the Global Mashup (ProcessApp). This is so that there is no possible confusion between the existing System "Applications" table and a user Auxiliary table, whose presence prevents promotion of such a Global Mashup. This was done by adding the table name to the list of reserved words.

2009r2 : deploy request fails with db error: ORA-00942: table or view does not exist

2. Create request which would be pending for this user. 3. In "Admin Console->Privileges->Request-> deploy to Next Stage" grant rule "Object is in the user's inbox or user has current role" 4. Deploy this request to next stage.

EM_* tables are not correctly upgraded for Oracle on and then deploy of Event Map fails

Errors similar to below may occur in your server.log at JBOSS startup: 2013-02-11 11:07:11,131 ERROR [main] [com.serena.em.ds.dao.db.HibernateSessionFactory] [::] -- Failed to parse event map. Error: Invalid byte 2 of 3-byte UTF-8 sequence. org.xml.sax.SAXParseException: Invalid byte 2 of 3-byte UTF-8 sequence.

2009R2 : Promote/deploy request fails with db error: ORA-00942: table or view does not exist

3. In "Admin Console->Privileges->Request->Promote to Next Stage" grant rule "Object is in the user's inbox or user has current role" 4. Promote/ deploy this request to next stage. Actual result:

SBM Version Diff

Differences Between Versions < table summary=" ... ... =0, mirror ... =2, mirror =1) ... ... .fa- table :before{ ... chain- broken :before{ ... ... =0, mirror =1) ... ... =2, mirror =1) ... ... .fa- table :before{ ... ... -chain- broken :before{ ... ... name=" table " unicode= ... ... > + < table >$SIGN ... ) table > ... > + < table >$SIGN ... ) table > ... ,section, table ,ul" ... + break ;case 3 ...

Error on deploy of a new Process App fails after upgrade from TeamTrack

An example of an error is as follows: ERROR -- Unable to update Table to next version - trying to add record for ordering. SQL statement: select A03ZO_TSM_SOFTWARE_PLATFORM.TS_ID, A03ZO_TSM_SOFTWARE_PLATFORM.TS_UUID from A03ZO_TSM_SOFTWARE_PLATFORM where A03ZO_TSM_SOFTWARE_PLATFORM.TS_ID=0 (TTexcIDS_EXC_UPDATE_TABLE_VERSION)

Deployment fails on Macros

01/03/2007 09:35:58: No macros to delete 01/03/2007 09:35:58: Updating records in table (TS_MACROS) 01/03/2007 09:36:11: Exception in CDeployMacroRecords::UpdateRecords()

Deploy gives error "Failed to schedule an activity"

ERROR mashupmgr.XmlBindingController -- Failed to schedule an activity. Couldn't store trigger: ORA-00942: table or view does not exist

Composer report definition against auxiliary tables fails at runtime - relational grid widget and embedded reports - ERROR: We're sorry, but the last operation caused an error

Newly-created relational grid widgets and embedded reports that point to auxiliary tables return an error in the browser after a process app is deployed . Note that this does not apply to widgets created before the upgrade to 11.1.

Pages [Next]

Knowledgebase

Find Answers

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Additional Assistance