Business Objects Cms Database Error Stw00226
Analytics Conference: Oct 18, Mastering SAP BI, Melbourne: Oct 23. STW00226 error in Installation of XI 3.0 Goto page 1, 2Next Search this topic...|Search General Discussion...|Search Box Select a search Explain These Choices... --------------------Recent Topics (All Forums) Unanswered Posts Register or Login to Post Forum Index -> General Discussion Author Message looksmeeForum AddictJoined: 08 Feb 2006Posts: 2674Location: Manchester Posted: Thu Jun 18, 2009 7:42 amPost subject: STW00226 error in Installation of XI 3.0 Hi We are popping up with the STW00226 error in Installation of XI 3.0, when checking the CMS database is up and running. Regards Siva.M Back to top hcroweForum MemberJoined: 20 Oct 2008Posts: 17 Posted: Thu Jul 23, 2009 3:02 pmPost subject: Re: STW00226 error in Installation of XI 3.0 I had the same problem. If you can connect via Oracle sql plus, then the error is probably bogus. I resolved the issue by moving my install to the C drive. I was attempting to install from a san attached drive. Makes no sense to return a tns error - but moving the install files resolved the error. Good luck Back to top Chris PohlForum AddictJoined: 18 Jun 2002Posts: 2848Location: da' burg Posted: Thu Aug 06, 2009 10:37 amPost subject: Re: STW00226 error in Installation of XI 3.0 silly thing to check ... but make sure you have the correct oracle database name specified_________________Chris Pohl Image link BOXI 3.1 SP3.2, LCM 3.1 SP3, BOBJ 6.5.SP4, PM 6.5.4 DB2 v8 via CAE 8.1.1.14, Oracle 10g and ODBC (of course) _________________________ Follow me on Twitter Search is Your Friend™ Back to top bonovice_08Senior MemberJoined: 22 Jan 2009Posts: 54 Posted: Thu Oct 22, 2009 5:52 amPost subject: Re: STW00226 error in Installation of XI 3.0 Hi All, I got the same error and I could connect tru SQLPLUS. I tried to install on the default MYSQL and later point it to the Oracle DB, but while i was installing it(on MY SQL), it said <...File not found> When i did a check on the installation files, i saw that i hadnt copied all the files needed for the BO installation. I had to re extract/copy the installation files and then installed it pointing it directly to the oracle DB. Bottom line is : make sure you have all the installation files you need to install BO. This worked for me! Back to top looksmeeForum AddictJoined: 08 Feb 2006Posts: 2674Lo
http://service.sap.com/bosap-support/Product Documentation on the Web http://help.sap.com/
+ productResults.length + resourceResults.length > 0 ? 'See all Search Results' : 'Full site search'}} > CA Support Online > KB Article Upgrade to CABI 3.0 failed with CMS database error: STW00226 Upgrade to CABI 3.0 failed with CMS database error: STW00226 Document ID:TEC525563 Last Modified Date:11/30/2012 ShowHide http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec525563.aspx Technical Document Details Products CA Spectrum Components REPORTING Description: The solution describes how to avoid this error during upgrading of BOXI R2 to CABI 3.0: CMS database error: STW00226 Database access error. Reason No data supplied for parameters in prepared statement. The problem is due to database access error, caused by specifying incorrect parameters to existing MySQL or specifying MySQL CMS database parameters business objects of previous BOXI R2 without the necessary creation of a new empty database and required granting of database access privileges. Solution: This problem can be avoided by selecting a new MySQL installation during the upgrade. Please refer to below screen capture that was taken during the upgrade on a Windows platform. In the case of anew MySQL database server installation, the installer creates a business objects cms completely different instance of MySQL and creates the required database with proper database access privileges. To use an existing MySQL of previous BOXI R2, prepare your database before upgrading to CABI 3.0 Create a new tablespace, schema, or database to act as the CMS database. The exact terminology will depend on the database platform. Create another database for the auditing database if you plan to enable auditing (or you can use the same database for auditing purposes). Create a new user account and password to be used by BusinessObjects Enterprise to access the CMS database. Create another username and password if you plan to enable auditing. Grant privileges to the user, where the database user can create, modify, and delete tables and create procedures. Record the name of the databases, the user accounts, and the passwords created, so that the details are available when you run the BusinessObjects Enterprise installer. For more details refer to CA Business Intelligence Implementation Guide, Chapter 2: "Prepare to Install", under the section Central Management Server Database Requirements and Preparation. All the CA Spectrum product documentation can be located at SupportOnline at: https://support.ca.com/irj/portal/DocumentationResults productID=1374