Skip to Content

SAP BO 4.1 SP5 CMC Repository error DB2 installation on Windows server 2012 error

Hi all,

We are trying to install SAP BO 4.1 SP5 on DB2 10.5 database in windows 2012 server, We are facing the below issue.

Regards,

Gowtham MN

ERROR2.JPG (60.1 kB)
Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Apr 06, 2015 at 06:36 AM

    Hi,

    Issue has been resolved.

    We have created table space & schema for CMS & ADS.

    Its working fine now.

    Thanks

    Reffered the below document.

    BOBI 4.0 Installation with separate DB2 Database & Customize database requirement

    Regards,

    Nethaji Palani

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 01, 2015 at 07:57 AM

    Hi Gowtham,

    Before starting BO installation we can create CMS and Audit Databases in DB2.

    ● DB2 Alias name - DB SID

    ● Account username

    ● Account password

    While Installing BO .->Reset existing database checkbox (recommended setting)

    Ensure that below steps from Installation Guide.

    4.2.1 Extra requirements for IBM DB2

    IBM DB2 has requirements that must be met before installing the BI platform:

    ● Ensure that the DB2 database is created with the following settings:

    Collating Sequence = "Identity"

    Codeset = "UTF-8"

    Territory = "<XX>"

    Replace <XX> with the code that is appropriate for your location. Consult your DB2 documentation for more

    information. If your DB2 database does not have the Collating Sequence = "Identity" setting, the

    user and user group objects may not sort as expected in the CMC.

    ● Create a user temporary table space before installing the BI platform. If you do not create a user temporary

    table space, the BI platform installation program will not be able to configure the DB2 database.

    For more information on user temporary table spaces in IBM DB2, see DB2 Basics: Table spaces and buffer

    pools in the IBM technical library: http://www.ibm.com/developerworks/data/library/techarticle/

    0212wieser/0212wieser.html .

    ● When using IBM DB2 to host an Auditing Data Store database, ensure that the page size for the auditing table

    space is set to a minimum of 8192 (8 KB).

    ● Ensure that the CMS system database is not partitioned. The Auditing Data Store database may be

    partitioned.

    Regards,

    V Srinivasan

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Mar 31, 2015 at 07:24 AM

    Hi Gowtham,

    Follow these steps:

    1.) make sure your user id used to connect to the database is following the naming rules for DB2:


    2.) Check the permissions on the following files in the instance ~/sqllib/security/ directory:


    ls -l /usr/<sid>/sqllib/security
    -r-s--x--x 1 root db2inst1 20374 db2ckpw*
    -r-s--x--x 1 root db2inst1 14387 db2chpw*


    3.) Stop the instance by running:

    db2stop


    4.) Log in as a user id that has root authority.

    5.) Issue the following command to update the instance:

    DB2DIR/<sid>/db2iupdt <sid>


    6.) Then start the instance by running:
    db2start

    7.) If you still see the error please also Make sure the catalog information on the client is correct.

    Hope this helps.

    Regards,

    Hugo

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Nethaji,

      This is what IBM says about your error:

      SQL30082NSecurity processing failed with reason reason-code (reason-string).

      Explanation

      An error occurred during security processing. The cause of the security error is described by the reason-code and corresponding reason-string value.The following is a list of reason codes and corresponding reason strings:

      24 (USERNAME AND/OR PASSWORD INVALID)

      The username specified, password specified, or both, are invalid. Some specific causes are:

      1. If you have recently changed permissions on DB2 critical files such as db2ckpw or moved to a new Fixpak, the db2iupdt command which updates the instance might not have been run.
      2. The username being used might be in an invalid format. For example, on UNIX and Linux platforms, usernames must be all be lowercase.
      3. An error might have been made in specifying the catalog information. For example, the correct authentication type might not have been specified or, if applicable, the remote server might not have been cataloged on the local system. For more information on authentication, search the DB2 Information Center (http://publib.boulder.ibm.com/infocenter/db2luw/v9) using terms such as "authentication".

      Check the above.

      Regards,

      Hugo

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.