Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML SQLNET.ALLOWED_LOGON_VERSION prevents SBM from connecting to the Oracle Database
At times it is necessary to use a specific Oracle version logon. This is accomplished by setting SQLNET.ALLOWED_LOGON_VERSION = (11,10,9,8) in the SQLNET.ORA file. When this is set as SQLNET.ALLOWED_LOGON_VERSION = (11,10), the SBM Application Engine is unable to connect to Oracle.
CMS-XML Unicode Upgrade Utility in SBM R4.01 or above resulting in error: Oracle database client must be 9i or 10g
When running the Unicode Upgrade Utility in SBM R4.01 or above, this error results: Oracle database client must be 9i or 10g The database client is a supported version so the error shouldn't be present. This can be caused by using a DSN with the unicode upgrade utility that is configured with the "Oracle for SBM" driver.
CMS-XML SBM 11.4.1 Hotfix 1: Repository gives error 500, Exchange web services, multi select values empty, blank form when SetFieldValue, Oracle max list is 1000
This hotfix should only be applied on top of SBM 11.4.1. If you are running a different version or if you have already installed a different SBM 11.4.1 hotfix, contact Serena Support.
CMS-XML SBM 2009 R4 crashes (stops responding) frequently when using an Oracle database
This problem was fixed in SBM 2009 R4.03. If you are running R4.03 and Oracle 10.2, check the version of the Oracle client that is installed on the SBM server. Any of the Oracle 10.2 drivers older than Oracle will also cause these problems.
CMS-XML Process the 10.x notification server uses to configure the database from a previous version of SBM/TT
3. After successful upgrade, NS inserts a record into NS_REGISTRY table with actual schema version (1 in this case) For Oracle : create table NS_REGISTRY (
CMS-XML SBM 11.4.1 Hotfix 5: Incoming emails not saved as note; Oracle expression error; Mail Client with Exchange; Repository fail to start; Missing transitions; Rich Text; Multi-user field; Creating Service Request; SRC Mobile submit
HF1 or SBM 11.4.1 HF3. If you are running a different version or if you have already installed a different hotfix, contact Serena Support.
CMS-XML SBM Configurator cannot connect to Oracle if there are no advanced security settings
10.1.3 Hotfix1, Hotfix3, 10.1.4, and, you must install and configure the OAS ( Oracle Advanced Security) module on the Oracle server or use a non-Dimensions version of Oracle instead.
CMS-XML Import Tracker 6.0 style project into SBM 2009R1 Oracle10.2.
These were in LONG RAW format in old versions of Oracle and Tracker. Upgrading Oracle (to 10.2x) and Tracker to version 8.x and then Upgrading the projects within Tracker to the 8.x style will convert the Long Raw column to BLOBs. Once the column is in BLOB format, the import to SBM works fine. Some non-US (US english language) environments have had issues with the Tracker upgrade to version 8 so they have been unable to let Tracker do the conversion of this column.
CMS-XML Upgrade DB to SBM 10.1.4 from TT 661 on Oracle fails
Install Complete the system upgrade (including running the Unicode Upgrade Utility and all other steps Install 10.1.4 and complete the upgrade to this version
CMS-XML Now that Oracle will charge for Java, what is the impact on SBM (SSM and SRC and RLC) customers?
Also, SBM has moved away from Oracle Java starting with SBM 11.5 so once you have upgraded to that version , you will not be using Oracle Java any more. NOTE: Because SSM (Service Manager), SRC (Request Center), and RLC (Release Control) are all solutions written on top of SBM, this document also applies.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs