cancel
Showing results for 
Search instead for 
Did you mean: 

Solution Manager 7.1 installation failing

symon_braunbaer
Participant
0 Kudos

Hello,

I am trying to install Solution Manager 7.1 on Oracle 10.2 and Linux. Unfortunately, at the very beginning of the installation, I am getting

a very bizzare error, during creating the users for the SAP system, here is an excerpt from my sapinst.log file:

TRACE  2013-08-05 20:47:30.334 [syuxctask.cpp:880]
       CUnixProcessManager::sap_waitpid(pid_t pid, int * pStatus, int options)
       lib=syslib module=syslib

Child process 5284 returned 0

ERROR  2013-08-05 20:47:30.355 [sixxcstepexecute.cpp:916]

FCO-00011  The step setUserEnvironment with step key |NW_Users_Create|ind|ind|ind|ind|0|0|NW_Users_Create_Do|ind|ind|ind|ind|usersCreateDo|0|setUserEnvironme

nt was executed with status ERROR ( Last error reported by the step: Assertion failed: in

function (role, readAccountData) {

if (readAccountData === undefined) {
    readAccountData = true;
}
NWUsers.trace("NWUsers.getAccountData(", role, ")");
this._initAccountData();
ASSERT(arguments.callee, this.haveAccountData(role), "role " + role + " is not created yet.");
var ad = this._readAccountDataFromKeydb(role);
if (readAccountData) {
    ad = this._readAccountData(ad);
}
var masterpwd = this.getMasterPassword();
if (ad.password == "" && this._useMasterPasswordForAccountData(ad) && ad.type == "USER" && masterpwd !== undefined && role != NWUsers.roles.J2EEGuest &&

!ad.locked) {

    ad.password = masterpwd;
}
NWUsers.trace("NWUsers.getAccountData(): ", dump_properties(ad));
return ad;

}

role ORA_SID is not created yet.).

TRACE  2013-08-05 20:47:30.380 [kdxxctaco.cpp:165]
       CKdbTableContainerImpl::syncToContainerFile lib=iakdblib

CKdbTableContainerImpl::syncToContainerFile start ...

TRACE  2013-08-05 20:47:30.420 [kdxxctaco.cpp:197]
       CKdbTableContainerImpl::syncToContainerFile lib=iakdblib

after creating out stream

I've tried to google, but no help, Note 972263 - Inst.NW 7.0(2004s)SR2/Business Suite 2005 SR2-UNIX/Oracle is not helpful either.

I've tried to run solely the preparation option for user creation. No luck 😕

I am  installing using the latest version of the SWPM, so I guess this shouldn't be some JVM issue... PLEASE HELP !!!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi simon,

there is nothing to worry. this is an sap bug and the solution is provided in note 972263

try the following

There are two ways to resolve this problem:


  • Modify control.xml and restart the installation

    1. Edit file control.xml in your installation directory (default
    sapinst_instdir).

    2. Search for "this.runCatproc = "

    3. Go to "script.execute_AbortOnFailure();" some lines below.

    4. Replace "script.execute_AbortOnFailure();" with "script.execute();".

    5. Restart Sapinst and choose "Continue with the Old Option"


  • Update the sapinst executable and restart the installation

    1. Download the newest sapinst executable from the Software Distribution
    Center as follows:


      a) Go to http://service.sap.com/swdc.


      b) On the right-hand panel, choose "Search for Software".


      c) Enter "sapinst" as search term.


      d) Choose the sapinst executable for your release (640, 700, 710).

    2. Replace the existing sapinst executable with the downloaded sapinst
    executable

  1. 3. Restart Sapinst and choose "Continue with the Old Option"

Regards,

Nag

symon_braunbaer
Participant
0 Kudos

Dear Nag,

thanks a lot for your reply, but unfortunately none of your suggestions can solve the problem.

Here are the details:

Your first suggestion - to edit control.xml:

I found "this.runCatproc = ". My file looks like this:

  this.runCatproc = function(sqlContext)

  {

    IA_ASSERT(sqlContext instanceof OraSqlContext,

              "OraDatabase.runCatproc: Argument sqlContext has to be an OraSqlContext");

    var stateMan = new OraDbStateManager3(sqlContext);

    stateMan.ensureDbIsAvailable();

    gui.update("catproc.sql...");

    var script = new OraSqlScript3(sqlContext.getDbHome() + "/rdbms/admin/catproc.sql",

                                   sqlContext,

                                   "FILENAME");

    script.addErrorIgnorePattern("ORA-00942");

    script.addErrorIgnorePattern("ORA-00955");

    script.addErrorIgnorePattern("ORA-01418");

    script.addErrorIgnorePattern("ORA-01432");

    script.addErrorIgnorePattern("ORA-01434");

    script.addErrorIgnorePattern("ORA-01918");

    script.addErrorIgnorePattern("ORA-01919");

    script.addErrorIgnorePattern("ORA-01920");

    script.addErrorIgnorePattern("ORA-01921");

    script.addErrorIgnorePattern("ORA-02289");

    script.addErrorIgnorePattern("ORA-02303");

    script.addErrorIgnorePattern("ORA-04043");

    script.addErrorIgnorePattern("ORA-06512");

    script.addErrorIgnorePattern("ORA-24001");

    script.addErrorIgnorePattern("ORA-24006");

    script.addErrorIgnorePattern("ORA-29807");

    script.addErrorIgnorePattern("ORA-29809");

    script.addErrorIgnorePattern("SQL-table");

    //    script.execute_AbortOnFailure();

    script.execute();

  }

  this.runCatalog = function(sqlContext)

  {

    IA_ASSERT(sqlContext instanceof OraSqlContext,

              "OraDatabase.runCatalog: Argument sqlContext has to be an OraSqlContext");

    var stateMan = new OraDbStateManager3(sqlContext);

    gui.update("catalog.sql...");

    var script = new OraSqlScript3(sqlContext.getDbHome() + "/rdbms/admin/catalog.sql",

                                   sqlContext,

                                   "FILENAME");

    script.addErrorIgnorePattern("ORA-00942");

    script.addErrorIgnorePattern("ORA-00955");

    script.addErrorIgnorePattern("ORA-01432");

    script.addErrorIgnorePattern("ORA-01434");

    script.addErrorIgnorePattern("ORA-01919");

    script.addErrorIgnorePattern("ORA-01920");

    script.addErrorIgnorePattern("ORA-01921");

    script.addErrorIgnorePattern("ORA-20000");

    script.execute_AbortOnFailure(); <- HERE ON YOUR SUGGESTION I've put script.execute();

  }

After restarting sapinst and choosing to continue, it came back with the following error, although I have successfully passed

the preparation session with creating the User IDs:

An error occurred while processing option SAP Solution Manager 7.1 Support Release 1 > SAP Systems > Oracle > Central System > Central System( Last error reported by the step: Assertion failed: in function (role, readAccountData) { if (readAccountData === undefined) { readAccountData = true; } NWUsers.trace("NWUsers.getAccountData(", role, ")"); this._initAccountData(); ASSERT(arguments.callee, this.haveAccountData(role), "role " + role + " is not created yet."); var ad = this._readAccountDataFromKeydb(role); if (readAccountData) { ad = this._readAccountData(ad); } var masterpwd = this.getMasterPassword(); if (ad.password == "" && this._useMasterPasswordForAccountData(ad) && ad.type == "USER" && masterpwd !== undefined && role != NWUsers.roles.J2EEGuest && !ad.locked) { ad.password = masterpwd; } NWUsers.trace("NWUsers.getAccountData(): ", dump_properties(ad)); return ad; } role ORA_SID is not created yet.). You can now:

Choose Retry to repeat the current step.

Choose Log Files to get more information about the error.

Stop the option and continue with it later.

Log files are written to /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS.

Your second suggestion: to replace sapinst with the latest version.

This isn't applicable either. On the marketplace I found SAPINST7202 from 13.06.2013.

I am using the Software Provisioning Manager, which I downloaded quite recently.

When I click Help / About in my sapinst, I see: SAPinst Version 722 OPT (Jul 5 2013 16:33:04).

This is more recent than the 13th of June...

Hence, I really have no further idea how to continue and will then proceed with installing the Solution Manager on a different DB. Most probably I'm gonna try DB2.

Former Member
0 Kudos

Hi Symon,

I am sorry that didnt work in your case. please try to follow the solman7.1 installation guides(installation using swpm and installation using sapinst.)  from below link.

https://websmp203.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000735220&_SCENARIO=011000358700000002...&

Regards,

Nag.

symon_braunbaer
Participant
0 Kudos

This message was moderated.

Answers (3)

Answers (3)

symon_braunbaer
Participant
0 Kudos

Hi everybody,

thanks for your replies and suggestions, unfortunately none of this could solve the problem:

@Sudheer G - I am installing the original oracle 10.2, which is coming with SAP. I have Oracle patch 10.2.0.5 prepared to install during the installation.

@ - I found Note 1300538 yesterday. The proposed solution:

Restart SAPinst using command line option SAPINST_SKIP_ERRORSTEP=true. On the "What do you want to do" screen, choose "Continue with the old option" returned exactly the same error.

From the thread you sent me:

./sapinst IS_HOST_LOCAL_USING_STRING_COMPARE=true SAPINST_USE_HOSTNAME=<hostname>

This doesn't work either, when I try it, I am getting the following error:


Inconsistent value of property SAPINST_USE_HOSTNAME for toplevel component NW_Onehost|ind|ind|ind|ind. Previous value: '', current value: '<hostname>'.

Perhaps this might be caused by the fact, that I've chosen not to do a domain installation ... ??

symon_braunbaer
Participant
0 Kudos

OK, I've tried a domain installation, by leaving the default "localdomain". But now I'm getting the

following (even more ridiculous) error:

Component OraDbBuild: Context parameter dbSid must be a nonempty string of length length = 8.)

I tried to google it, but nothing at all... P;LEASE HELP MEEEEEEE..... 🙂

One small addition: I am still getting the following warning:

Soft resource limit nofile (limit on files one process can open at a time) for group sapsys

should have a value larger than or equal to 4096 on Linux if a Java EE engine is used. Current

value in /etc/security/limits.conf: not available. See also SAP Notes 722273 for Red Hat, 767814

for SLES 8, or 797084 for SLES 9. (Updated 2005-06-24)

I have this in my /etc/security/limits.conf:

@sapsys  hard   nproc  32800
@sapsys  soft   nproc  32800

but still getting the warning, not sure whether it's related...

Former Member
0 Kudos

Hello,

After adding these limits you have to trigger the command sysctl -p for the parameters to effective.

Best Regads

Bhupesh

Former Member
0 Kudos

hi,

error as,

role ORA_SID is not created yet.).

Try the sap note 1300538. the solution could be as below as per the sap note

later i found this, chk this work arround too http://scn.sap.com/thread/3366486

Thanks

Jansi

Former Member
0 Kudos

May I know the exact oracle version you are installing?