ECC on Different Database

[Former Member]

Hi all,

Greetings!!

We are planning to install ECC DEV and ECC QAS on Oracle Database and ECC PRD alone on HANA Database.

Can we follow this approach or will it have any serious impacts technically and functionally other than administration point of view.

Looking forward for your valuable suggestions.

Thank you,

Regards,

KE.

[Former Member · Accepted solution]

If you are planning on using any HANA functionality in production, you are going to need somewhere to test it. You are going to need somewhere to develop it. If DEV and QA are non-HANA systems, you have nowhere to do that.

Software has bugs, even databases. Different databases will have different bugs. How will you investigate a potential HANA bug, if the only system you have running HANA is your production system? How will you test that a patch fixes the bug if the only HANA system you have is your production system?

All-in-all, having DEV and QA be so radically different in architecture is not a good idea. You can do it, but you really shouldn't. I wouldn't do it even if HANA wasn't involved. I don't like running different patch levels of DB, kernel or OS, let alone different databases.

Does that help?

Steve.

[Former Member]

Hello Elan,

I would never recommend such a configuration. Your development, QA and production systems must be identical in terms of:

*OS type and patch level

*Database type and patch level

*Kernel version and patch level

*SAP version and stack level

Otherwise tests, you do in your dev and QA, would be inappropriate.

Kind regards,

Serhat

[Brindavan_M]

Hi,

If your going with SAP HANA database in production, then your system need to go sysbase database as suggested by SAP. This is which will not affected your testing environment. DB architecture some thing need to match with your three systems landscape for business to troubleshooting the issue easily .

Thanks,

BM

[Reagan]

Technically it is possible to have such a setup but like Steve said it is not a good practice. Testing is important and your test environment should be similar to your production. Doing a system copy (refresh) from production to test is not possible if they both are on different databases. Also it would be difficult to identify DB related issues when doing SP/EHP updates or release upgrades and you will end up having surprises if the production setup is different from other systems in the landscape.

RB