cancel
Showing results for 
Search instead for 
Did you mean: 

Migration to Oracle Exadata using SAPinst

Former Member
0 Kudos

Hello,

Has anyone done migration to Exadata using SAPINST..? We are trying to import database to Exadata using SAPINST'S Database instance option of distributed system copy and we are facing issue while Database is being created in Exadata/ASM.

We have prepared both the nodes and now we are trying to import our Database using R3load method. In the phase DATABASE CREATION, we are

facing issues with control file creation in the ASM disk group. It gives Error message: "ORA-01501: CREATE DATABASE failed ORA-00200: control

file could not be created ORA-00202: control file:'+DATA_MCFL/mps/cntrlmps.dbf' ORA-17502: ksfdcre:3 Failed to create file+DATA_MCFL/mps/cntrlmps.dbf ORA-15001: diskgroup "DATA_MCFL" does not exist or is not mounted ORA-15204: database version 11.2.0.0.0 is incompatible with diskgroup DATA_MCFL Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production With the Partitioning, Real Application Clusters, Automatic Storage Management,OLAP, Data Mining and Real Application Testing options . SOLUTION: Formore information, see ora_sql_results.log and the Oracle documentation.)."

we have checked our ASM disk group compatibility and it has been set to

11.2.0.2.0 ,We referred Oracle note ID no. 1468931.1 and tried to check the

compatible parameter in the init<SID>.ora file and also checked the

templates .dbt and .dbca files. We tried to change the compatibility to

11.2.0.2 and re-tried, but it did not help.

Kindly help us in resolving the issue.

Regards

Shivaprasad D

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

The error is quite clear:

Database version 11.2.0.0.0 is incompatible with diskgroup DATA_MCFL

As Mustaf said before SAPinst always tries to create database with database compatible = 11.2.0.0.0.

But the rest of his reasoning are not exactly right.

Since your ASM diskgroup has created with 11.2.0.2.0 already, (above the 11.2.0.0.0 ) it does not support 11.2.0.0.0 database anymore.  So ASM diskgroup compatibility should be set to the lowest version of the database you want to created with.

The solution will be either change the database compatible parameter in init.ora/spfile.ora to the same or higher version of ASM diskgroup compatible or create diskgroup with lower compatible.

Unfortunately you cannot lower diskgroup compatible after creation, you can always change it higher later.

Unless you want to recreate diskgroup, you will have to adjust your database parameter file.

BTW, SAP recommends using database compatible to 11.2.0.2 in ASM configuration. (unless you are using GG) Which means you will have to adjust db init.ora/spfile before you let SAPINST to create database if SAPINST does not create an init.ora/spfile.ora with right parameter for compatible.

Certainly to address a SAPINST issue is beyond the scope of this discussion.

Thanks,

Michael S. Wang

Former Member
0 Kudos

Dear Michael,

Thank you for your detailed explanation ,This is what exactly the dilemma in which we are in.

Even we tried changing the init<SID>.ora file parameter with no success,it throws up below error

"“ORA-01092: ORACLE instance terminated. Disconnection forced ORA-01501: CREATE DATABASE failed ORA-00349: failure obtaining block size for '+DATA' ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mounted .”    

it seems SAPinst is now trying to create the database on default disk group (+DATA) which we do not have created in ASM(ours is +DATA_MCFL).

apart from above we do observe one more potential issue with init<SID>.ora  created by SAPInst , for the parameter "Log_archive_Dest_1" the default value is +ARCH. But we do not have +ARCH ASM Disk Group created in Exadata and it is recommended to keep archive in +RECO disk group as per the white paper  .

We are awaiting for SAP's reply , We will keep you updated.

Thank you once again for well explained description.

Regards,


Former Member
0 Kudos

Hi,

We got replay from SAP and they have referred us to - Note 1773593 - CREATE DATABASE on ASM fails with ORA-15204.

According to this Note we have to change the value of database parameter COMPATIBLE in SAPInst (advanced mode) and so we want to change this parameter to COMPATIBLE=11.2.0.2.0 as our ASM disk group compatibility is already set to 11.2.0.2.0.

But we could not able to locate this parameter in any screens of SAPinst. we have checked under both custom mode and Advanced DB configuration mode with no success.

Can any body help us to locate this parameter option in SAPInst.? Note that we are using SAP installation Master "NW 7.31 Kernel, Inst.Master,Upgr.Master Solaris x64(51042225_39)".for the installation.

Regards,

Shivaprasad

Former Member
0 Kudos

Shivaprasad,

As I've explained and recommended above, you can edit the parameter manually on the relevant folder with the right value and continue on SAPINST, that's going to solve your issue. Please give a try.

Best.

Mustafa Aktas

Former Member
0 Kudos

Dear Mustafa,

We tried changing the /oracle/SID/112/dbs/initSID.ora file  parameter with no success,it throws up below error.

"“ORA-01092: ORACLE instance terminated. Disconnection forced ORA-01501: CREATE DATABASE failed ORA-00349: failure obtaining block size for '+DATA' ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mounted .”    

it seems SAPinst is now trying to create the database on default disk group (+DATA) which we do not have created in ASM(ours is +DATA_MCFL).

Can you please let us know where else we need to maintain this parameter.

Regards,

Former Member
0 Kudos

Shivaprasad,

I don't know if you've ever intended to open the SAP ASM best-practices and Exadata for SAP best-practices guide, both of that explains the SAP's best practices to name the disk-groups, please make sure you need the guides and the step-by-step documentations there, and raise your questions referring relevant pages.

Without obeying the best-practices and recommendations and already completed documentation based on the real expertise, you'd not be able to achieve your goals easily and it'd be painful for everybody from your (implementer) customer and vendors (SAP and Oracle) side.

Best.

Mustafa Aktas

Former Member
0 Kudos

Shivaprasad,

In addition, that seems that you also don't read SAP OSS Notes, referring to "SAP Note 1619343 - SAPinst for Oracle Exadata on Oracle Linux and Solaris X86", you should use the right SAPINST which does seem to be the first and biggest mistake!

There's new name/concept for SAPINST which is Software Provisioning Manager (SPM), since you are using the wrong version of SAPInst.

Please download version which contains all the enhancements from SAP marketplace following;

 

Support Packages -  SL Toolset -  SL Toolset 1.0  - Entry by component  - Software Provisioning Manager

Best.

Mustafa Aktas

Former Member
0 Kudos

Dear Mustafa,

First of all thank you for your efforts in helping us.  It is not true that we have not referred the documents which you are referring to; we have read most of the white papers available from Oracle regarding ASM/RAC/Exadata including those you have mentioned.

Our issue is that, any of the document does not describe a procedure for importing SAP database using SAPinst (R3load) . Hence we are trying to improvise on the data available on the various Documents to get the things done. While doing so we are getting in to the issues that we are posting it here hoping that someone could have faced similar issues.

Furthermore to our query regarding ASM Disk group naming convention, we could not find any document that specify the disk groups should be named +DATA or +RECO exclusively. Yes there are few lines in Page number 5 of the white paper – “An Oracle White Paper-July 2011 Using SAP NetWeaver with the Oracle Exadata Database Machine -A Best Practices Guide”   which says

“In line with the standard Oracle Exadata setup you should have at least one ASM Disk Group“+DATA” and another ASM Disk Group “+RECO”. The DATA Group should contain all data files, control files, online redo log files, spfiles, OCR and voting disks. The RECO Group should contain temporary files, archive logs, flashback files and backups.”

But the above lines sounds more like we should at least have one disk group for DATA and one for RECO rather than we should have disk group named +DATA and +RECO .

Regarding the SAP Note Note 1619343 - SAPinst for Oracle Exadata on Oracle Linux and Solaris X86 , yes we have  referred this note  and in fact this is one of the first note that we referred as it talks about SAPinst support for Exadata .

According to above note have downloaded and used Software Provisioning Manager (SPM) and completed the step “Exadata/ASM Database Instance Preparation”,This just prepares the Exadata instance which we have completed as a first step. After completing this step only we are using the above mentioned SAP installation master (which is for SAP Netweaver 7.3 including Enhancement Package 1) and it is mentioned in the same Note that we can use/find the same installation components also on this Installation Master DVD.

One more reason why we have opted to use this DVD instead of SPM is that since we are trying to do a system copy (R3 Load based) from current system to Exadata and  we could not locate system copy option in SPM.

Now for the update on this issue –

We got reply from SAP regarding where to maintain the COMPATIBILTY parameter – this is what they say –

“you need to download the newest sapinst (Software Provisioning Manager 1.0) to set the compatible parameter in the db advanced section. For your version you can also modify the INITSID112.ORA template on the installation master dvd under .../COMMON/INSTALL/ORA/INITSID112.ORA.
There you can overwrite the parameter to the correct value compatible = 11.2.0.3.0.
Then you need to start the installation from the beginning.”

Following the above instructions we are now able to pass through COMPATIBILITY issue. But then we are stuck with another issue similar to issue mentioned  by Mr Beymen Admin in this thread… SAPInst is now throwing the error for Online redo logs when it is creating database, below is the extract from the log –

“Disconnection forced ORA-01501: CREATE DATABASE failed ORA-00349: failure obtaining block size for '+DATA' ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mounted”

From the above we believe now SAPInst is trying to create redologs in +DATA  which we never had (ours is +DATA_MCFL) .In any case we have decided to recreate the ASM disk groups by name  +DATA and +RECO and give a try.

Will this work ? we will come to know in a day or two. Till then, we will have to wait. We will keep you posted.

Regards,

Former Member
0 Kudos

There is one document on migration to exadata using sapinst. follow http://scn.sap.com/docs/DOC-31409

and a best practices guide - http://scn.sap.com/docs/DOC-15892

Former Member
0 Kudos

Sunil, I already did refer to those whitepapers above, you'll see if you'll read the entire thread and messaging.

Shivaprasad,

May I kindly ask you first if you know there is currently no support with Exadata for system copies!?

Please do not rename the disk groups. The latest SAPInst version allows you to use any ASM disk groups!

What is the SAP OSS call number for all these problems?

Best.

Mustafa Aktas

Former Member
0 Kudos

Gents,

Most probably, SAPInst version you are using has a bug when creating redo log files if you're getting the error below;

“Disconnection forced ORA-01501: CREATE DATABASE failed ORA-00349:

failure obtaining block size for '+DATA' ORA-15001: diskgroup "DATA"

does not exist or is not mounted ORA-15001: diskgroup "DATA" does not exist or is not mounted”

There supposed to be a new version uploaded to the marketplace within the next week. Please follow!

Best.

Mustafa Aktas

Former Member
Former Member
0 Kudos

Shivaprasad,

Please also don't forget to check SAP OSS Note: 1775313

Best.

Mustafa

Answers (5)

Answers (5)

Former Member
0 Kudos

Dear all,

Thank you all for the valuable inputs...this is to update you all on this issue..... to summarize on the the Issue we have raised in this thread, can be broken in to two Issues...

1. Database version 11.2.0.0.0 is incompatible with diskgroup DATA_XYZ - We got this issue resolved with help of SAP and the solution for the same is in this Note - Note 1773593 - CREATE DATABASE on ASM fails with ORA-15204

2. SAPinst  trying to create the database on default disk group (+DATA ) which we do not have created in ASM(ours is +DATA_XYZ). - Solution for this is documented in Note - Note 1775313 - Installation on ASM with SAPINST 7.0X fails

We believe the newer version of SAPInst would include patches for this issues soon.

and now in continuation of the above  we are now stuck in the phase of "create/check tablespaces "

It is giving the below error -

"Database Instance( Last error reported by the step: Unable to create the tablespaces. DIAGNOSIS: There is not enough free disk space: Mount point | space required | space available | SAPDATA directories / | 243210 | 17025.3 | 2,7,3,4 . SOLUTION: Make more disk space available.). You can now:"

We have checked our ASM disk groups and they have plenty of disk space available.

Any inputs regarding this issue would be of great help.

Regards,


former_member301345
Discoverer
0 Kudos

Dear Shivaprasad,

Stop the sapinst and then  create tablespaces manually and start sapinst with option SAPINST_SKIP_ERRORSTEP=t  because sapinst try to create database on local disk not in ASM disk thats why yo got an error in this step.

Best regards,

Eren Yeniay.

former_member301345
Discoverer
0 Kudos

Dear Shivaprasad,

You should change the compatible level of the SAP DB, I have changed the compatible parameters from /oracle/SID/112/dbs/initSID.ora file.

Best regards.

Eren.

Former Member
0 Kudos

Dear Eren,

We tried changing the initSID.ora file also with no success. We are getting the error as mentioned in replay to Michael Wang ( see below) .

We are still awaiting SAP's reply, kindly let us know if you get any solution.

Regards,

Former Member
0 Kudos

Dear Eren,

I think we are now stuck with same error that you are having. Did you get any resolution for it..?

For the earlier compatibility issue we got resolution from SAP as mentioned in this thread  and we have posted this issue as well with them.

We are curious to know from your end.

Regards,

former_member301345
Discoverer
0 Kudos

Dear Shivaprasad,

Did you solve this issue?

I have a same problem for Sap Installatıon on exadata with no default asm disk groups.

I have changed the data files and control files location with in steps advanced db configrations however sapinst gave an error for Online redo logs when it was creating database.

If you solve this issue  please let me know how you can pass it.

And also I am curious about what  the solutions of sap and oracle are.

I am looking forward your reply.

Best regards Eren

Former Member
0 Kudos

Dear Beymen,

We are still awaiting for the solution from SAP/Oracle. We will certainly let you know for the solution if we get any.

From your post, It seems that you have already passed the  initial database creation step but we are stuck at this step only.

can you please let us know the ASM disk compatibility parameter maintained in your Exadata..?

below are the out put of our Exadata ...

Regards,

Former Member
0 Kudos

Hi gents,

I want to underline one more time kindly, you're not reading the relevant document/whitepaper to run SAP on ASM and on Exadata.

Please make sure that you're reading one more time all the documents located at SCN Oracle community ASM page: http://scn.sap.com/docs/DOC-7971

Inside the first "SAP Databases on Oracle Automatic Storage Management 11g Release 2" guide "Oracle ASM Compatibility Attributes" section, "Moving your SAP Database to Oracle Automatic Storage Management 11g Release 2 A Best Practices Guide" guide "Oracle ASM Compatibility Attributes" sections.

So please make sure that when creating the disk groups (or changing it afterwards) for SAP that the compatible parameters are correct. This is an SAP requirement (similar that you need to specify the correct database character-set for SAP or many such other parameters needs to be applied among best practices).

More particular it is Exadata specific as ASM creations on non-Engineered Systems do create all disk groups with 11.2.0.0.0, it should be at least 11.2.0.2 if you'd like to build-up 11.2.0.2 DB on top of that ASM filesystem:

Best.

Mustafa Aktas

Former Member
0 Kudos

Dear Mustafa,

Thank you again for the info, We have already gone through the White papers that you have mentioned above. following is what we believe, the issue in our case, Kindly correct us if we are wrong -

  • Since we are trying to create and load database through SAPInst and SAPInst always creates all databases with 11.2.0.0. We should configure/create the ASM disk groups with  compatible parameters set to 11.2.0.0
  • If above assumption is correct , then it seems that we need to scratch the current ASM disk group and rebuild it with compatible parameters set to 11.2.0.0( as our current ASM Disk group compatible parameters are already set to 11.2.0.2.0 and we can not downgrade this parameters without rebuilding the disk group)
  • We are hoping, SAP has some workaround to address this issue and that is where we are waiting for their reply

Regards,

JimSpath
Active Contributor
0 Kudos

I checked with one of the "SAP On Oracle" experts, and I'll paraphrase their response:

  • Is the disk group named /DATA_MCFL?
  • Do you have the Exadata start up kit?
  • Where are you from (your SCN profile page, where contact information should be, is empty)?

Jim

Former Member
0 Kudos

Hi,

  • Is the disk group named /DATA_MCFL?

               Yes, The disk group is named as DATA_MCFL.

  • Do you have the Exadata start up kit?

               We are not sure about it. Checked with the client and they say they are in to Platinum Support for Exadata but not sure whether this covers the start up kit services.

  • Where are you from (your SCN profile page, where contact information should be, is empty)?

               I am from India. i have updated the same in my profile.

Regards,

Former Member
0 Kudos

Hi Shivaprasad,

That looks like ASM compatibility issue.

Referring the Oracle docs http://docs.oracle.com/cd/E11882_01/server.112/e18951/asmdiskgrps.htm#CHDDIGBJ the error that you've got seems to me that SAPINST is not able to create relevant parameter in spfile/init.ora file.

You'd better concentrate on ASM's disk-group compatibility concept which is been set during the creation of disk group and if you'll set that for example 11.2.0.2 then they'll prevent creation of any DB with the version of 11.2.0.1 which is lower than that version.

Since you error seems SAPINST is trying to create DB with 11.2.0.0 version, that might be your barrier here.

Please open the support case and let me know your case # if you'd like to get more info.

Best.

Mustafa Aktas

Former Member
0 Kudos

Dear Mustafa,

We have raised the support case with both ORACLE and SAP -

Oracle Case # - 3-6251553951

SAP Case # - 887722/2012

We appreciate your help regarding this.

Regards

Shivaprasad D

Former Member
0 Kudos

Shivaprasad,

You need to read the ASM/SAP related whitepapers and all relevant notes as the best-practice before starting such a migration.

Please take a look at SAP/ASM best-practices guides such as "Moving your SAP database to Oracle 11gR2 ASM" and face the situation that the administrator needs to take care of ASM compatible parameters.

SAPInst always creates all databases with 11.2.0.0.  This is the default for both filesystems and ASM!

And was implemented when SAP was certified for 11g R2.

This is an ASM restriction as it not an issue with SAP on filesystems.

So please make sure that when creating the disk groups (or changing it afterwards) for SAP that the compatible parameters are correct. This is an SAP requirement (similar that you need to specify the correct database character-set for SAP or many such other parameters needs to be applied among best practices).

More particular it is Exadata specific as ASM creations on non-Engineered Systems do create all disk groups with 11.2.0.0.0.

FYI, hope that helps. Best.

Mustafa Aktas

Former Member
0 Kudos

Dear Mustafa,

Thank you for the inputs. We will  wait for the suggestions from SAP as well and then proceed . We will keep you posted.

Regards

Shivaprasad