cancel
Showing results for 
Search instead for 
Did you mean: 

System copy with SLTOOLSET, MCOD installation error => OraSqlContext : dbSidOrSrcObject and dbHome are not valid

ACE-SAP
Active Contributor
0 Kudos

Hello,

I'm performing a BW 7.31 system copy on Windows OS (2008R2) with "Software Provisioning Manager 1.0 SP 01".

The ABAP stack (SID:BEW) is copied and running on target system, DB (oracle 11.2.0.3), listener are up and running.

When I start the Java import (SID:BEJ) on target just after selecting MCOD option and giving the password for the SAPSR3DB java schema user I get the following error:

SchemaPostChecksJava was executed with status ERROR ( Last error reported by the step: Assertion failed: OraSqlContext constructor: arguments dbSidOrSrcObject and dbHome are not valid.).

SAPinst is able to reach the DB and run queries as I did have some ora_query*.res files that proves that SAPinst was for instance able to get the list of the defined users/schemas.

Looking in log files the Oracle Home is set to the correct value.

I did try to run the import both using administrator account (no env var set) and ABAP user account (SIDadm) I get the same error.

I'm opening an OSS message but if any expert has a clue, any help is welcome

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

ACE-SAP
Active Contributor
0 Kudos

Hello

I've just received a final answer from SAP

I'm sorry I cannot upload the file it is to big (8Mb) and SCN does not accept zip file (such a pity for a company that is making so much money and seems to ivest so few in the community site... but this is an other problem  😉 )

Good luck...

22.01.2013 - 13:34:55 CET - Reply by SAP     

Dear customer,

i have upload a new control.xml file which will fix this issue.

Please replace this control.xml file to your downloaded swpm dvd in the

folder

...\PVIND\XML7XX\control.xml.

Then you need to start the installation from the beginning.

We will update this fix also on service marketplace as soon as possible.

The fix in control.xml is the following: (oracleHome should replace withdbHome in 2 lines)

1.

search for c_nw_oracommondia and then replace

oracom.setAndCheckABAPSchemaUser(context.get("ABAPSchema"),

context.get("osUser"),

context.get("thread"),

context.get("oracleHome"));

with

oracom.setAndCheckABAPSchemaUser(context.get("ABAPSchema"),

context.get("osUser"),

context.get("thread"),

context.get("dbHome"));

2. and few lines later

search for

oracom.setAndCheckJavaSchemaUser(context.get("JavaSchema"),

context.get("osUser"),

context.get("thread"),

context.get("oracleHome"));

and replace with

oracom.setAndCheckJavaSchemaUser(context.get("JavaSchema"),

context.get("osUser"),

context.get("thread"),

context.get("dbHome"));

Former Member
0 Kudos

Thanks so much Olivier!!!!

I open a message two days ago, but still I don´t have any answer.

I've just tried modifying the control.xml file and it works!!

Thanks for all,

Ana.

symon_braunbaer
Participant
0 Kudos

Fine, but I am having the same problem now, with the most recent SWPM for HP-UX IA64 and the structure of the file has changed and this solution doesn't work anymore.

Could you kindly advise on what to do now ?

Thank you!

Answers (3)

Answers (3)

ACE-SAP
Active Contributor
0 Kudos

Hello

So it is a bug...

SAP did provide me a keydb.xml file and I just had to replace the original file and keep on with the copy process...

It's importing the data right now.

Find the file in attachment, It should work for all...

Former Member
0 Kudos

Thank you Oliver, but unfortunately the keydb file is specific for your installation/copy.

I will need to open a message to SAP. Could you please tell me your message support number, to reference it in my note. Maybe this way the solution will come faster.

Thanks a lot!

Ana.

ACE-SAP
Active Contributor
0 Kudos

Sorry

I did not check the file content, you're true it contains hardcoded variables.

Ref of my message to OSS support is

System copy with SLTOOLSET, MCOD installation error => OraSq ( 31685 / 2013 )

Former Member
0 Kudos

Hi,

Can you please try to set SAPDATA_HOME as well as ORACLE_HOME in the system environmental variable in addition to  user environmental variable and try again.

Please check and share your feedback.

Thanks and Regards,

Vimal

ACE-SAP
Active Contributor
0 Kudos

Hi Vimal

I've already tried to play with env var and set all required ones. It is not fixing my issue.

In fact I did already get that error with ABAP system copy. I had to restart the copy after a 1st run that failed because of access error to the export.

I did uninstall the SAP instance but keep the DB. I did get the same error

For ABAP

ERROR 2013-01-08 10:11:59.643 [sixxcstepexecute.cpp:995]
FCO-00011 The step SchemaPostChecksABAP with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_CreateDB|ind|ind|ind|ind|createdb|0|NW_OraDBCheck|ind|ind|ind|ind|ora|0|NW_OraDBMain|ind|ind|ind|ind|main|0|NW_OraCommonDiaSrv|ind|ind|ind|ind|dia|0|SchemaPostChecksABAP was executed with status ERROR ( Last error reported by the step: Assertion failed: OraSqlContext constructor: arguments dbSidOrSrcObject and dbHome are not valid.).

 

For Java

ERROR 2013-01-11 10:29:12.55 [sixxcstepexecute.cpp:995]
FCO-00011 The step SchemaPostChecksJava with step key |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_CreateDB|ind|ind|ind|ind|createdb|0|NW_OraDBCheck|ind|ind|ind|ind|ora|0|NW_OraDBMain|ind|ind|ind|ind|main|0|NW_OraCommonDiaSrv|ind|ind|ind|ind|dia|0|SchemaPostChecksJava was executed with status ERROR ( Last error reported by the step: Assertion failed: OraSqlContext constructor: arguments dbSidOrSrcObject and dbHome are not valid.).

I was not able to go through even with setting all the env. var.

I did then drop the DB and the instance and restart the ABAP copy from scratch.

For the Java stack I get stuck with the same error but that time I cannot drop the ABAP Db 😉

Thanks for your help

former_member185239
Active Contributor
0 Kudos

Hi Oliver,

If you want you can make the copy of control.xml and replace the lines dbSidOrSrcObject with BEJ and dbHome with SAPDATA_HOME path in the control.xml

If not use the latest SLTOOLSET.

With Regards

Ashutosh Chaturvedi

ACE-SAP
Active Contributor
0 Kudos

Hi Ashutosh

Thank you for your advice

I've just tried but I still get the same error.

Best regards

rayko_aben
Explorer
0 Kudos

Hi Oliver,

did you recieved an answer from SAP? I got the same problem during a fresh MCOD installation of java application server onto an existing oracle 11.2.03 database.

Kind regards

Rayko

ACE-SAP
Active Contributor
0 Kudos

Hello Rayko

I did open a message one week ago, went through all the stupid questions from support level 1 and 2 and SAP is currently connected on my system...

Thus it definitely looks like a bug.

I'll keep you inform & update the thread as soon as I get a solution from support

Best regards

rayko_aben
Explorer
0 Kudos

Hello Oliver,

thanks a lot for quick reply.

It seems to be a bug. I opened a message too. So I still have to pass 1st and 2nd level 😉

Let's see who is the winner...

I will update this thread too.

Best regards

Rayko

Former Member
0 Kudos

Hello!

I have the same problem.

I have installed the ABAP instance of SAP ERP 6.0 EHP5 with the 70SWPM1.0 (70SWPM10SP01_1-20009707.sar) without any problems.

Now, i am trying to install a Java instance, but just after the DB screen parameters, I get the error:

Assertion failed: OraSqlContext constructor: arguments dbSidOrSrcObject and dbHome are not valid

In the logs of sapinst_instdir, there are no more explicit errors.

Please let us know if you have a solution.

Thanks!!!

Former Member
0 Kudos

Hi Olivier,

The reason may be caused by a problem in "control.xml". Even though the version is mismatch, could you check the Note 786673 - SAP Web AS 6.40 SR1 on Windows: Oracle with the search for "dbHome are not valid" string

It may help to solve the problem.

Best regards,

Orkun Gedik

ACE-SAP
Active Contributor
0 Kudos

Hi Orkun

I did already check that note but SAPinst configuration files has changed a lot from 640 to 731 !

This note does not provide useful information

Thanks

Former Member
0 Kudos

Of course I am aware that there is a big difference between releases. I think that this problem is caused by control.xml file. So, you updated latest sltoolset from SAP Marketplace?

Best regards,

Orkun Gedik

ACE-SAP
Active Contributor
0 Kudos

I agree with you I think the error might be in the control.xml file... as far as I was not able to find errors arrounf env. var.

I did found that error message twice in the control file but it does not provide useful info...

The file is too big to be attached and SCN does not accept ZIP attachment ;-(

Than you for help

==============================================

 

// set this._force equal true when dbSidOrSrcObject more than 3 character (for example in RAC installations)

if ( dbSidOrSrcObject.length > 3)

this._force = true;

 

if ( parseBool(this._force) ) {

this._dbSid = dbSidOrSrcObject;

[...]

 

}

 

else

{

IA_ASSERT(this._checkDbSidDbHome(dbSidOrSrcObject, dbHome),

"OraSqlContext constructor: arguments dbSidOrSrcObject "

+ "and dbHome are not valid.");

this._dbSid = dbSidOrSrcObject;

this._dbHome = dbHome;

this._environmentVariables =  

[new OraEnvironmentVariable("ORACLE_HOME", this._dbHome),

new OraEnvironmentVariable("ORACLE_SID", this._dbSid)];

 

}

==============================================

 

if (dbSidOrSrcObject.osAccountInfo != undefined)

{

this._osAccountInfo = new OraOsAccountInfo(dbSidOrSrcObject.osAccountInfo);

}

if (dbSidOrSrcObject.dbUserInfo != undefined)

{

this._dbUserInfo = new OraDbUserInfo(dbSidOrSrcObject.dbUserInfo);

}

else

{

IA_ASSERT(this._checkDbSidDbHome(dbSidOrSrcObject, dbHome),

"OraSqlContext constructor: arguments dbSidOrSrcObject "

+ "and dbHome are not valid.");

this._dbSid = dbSidOrSrcObject;

this._dbHome = dbHome;

this._environmentVariables =

[new OraEnvironmentVariable("ORACLE_HOME", this._dbHome),

new OraEnvironmentVariable("ORACLE_SID", this._dbSid)];

}