Skip to Content

How to drop developer users on HANA?

Hi at all,

I'm the HANA Admin DB of a health care company in Spain.

Few months ago there was a project on my company involving HANA/ERP/BW.

I arrived at SAP BASIS when the developers (from outside Business consulting) had begun few months ago, so I wasn't the guy who prepared HANA for this project.

Now all of the five junior consultants aren't on our company, the project it's over but they used their personal user to create all parts of the project.

"Fortunately" (and I say in quotation marks) the main schema of the project was created using SYSTEM user (not personal user but... SYSTEM...). They created the SCHEMA on development, integration and production with SYSTEM user.

Now, auditing tells me not to have personal users of people who aren't on our company, so I have to erase them in one way or another.

I made some SQL to know how many objects they have and my question is...

What can I do?

They don't use the transports until I arrived because they don't use integration system... and all of the elements on DEV aren't with the same owner on INT and on PROD.

For testing I make a user test on DEV, with that user I created an schema and a table on it. I also created an object in a new package created by this user (a CV) and later I tried to erase this user using only restrict, not cascade.

The message returned is that I can't use restrict erase.

I understand that if I delete a user who owns a lot of objects and schemas, all of this remains inactivated ¿? how I can reactivate them?

All of those five developer guys will be forever on our HANA because we cannot switch the ownership to another user?

I had read a lot on SCN, support, help, but I'm in the same...

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Mar 21, 2017 at 12:50 AM

    Ok, in fact, the situation is a lot worse than what you describe: if you delete one of the development users that own objects (with cascade) then these objects will be deleted, too.

    As a short-term fix, deactivating the users is the right thing to do. The users won't be able to login, but all the objects that belong to them will still be valid and usable by anyone with the right privileges.

    The next step obviously has to be finding a way out of this mess.

    One option would be to gather all objects, recreate them with a technical user and fill the data from the original structures. That's tedious but would make the scenario easier to overlook.

    But if you're already at doing this, I'd probably invest a bit more time and retrofit the existing development into design-time artefacts.

    Simply switching ownership is not that easy to do, which is why HANA doesn't support it.

    I know - these are not great news, but the system is in exactly the mess, we've warned folks about for years, and cleaning it up is probably your best possible move.

    Add comment
    10|10000 characters needed characters exceeded

    • One option would be to gather all objects, recreate them with a technical user and fill the data from the original structures. That's tedious but would make the scenario easier to overlook.

      You're right, that's the way that I was thinking about. It will be a lot of work but I think it's the way to solve this bad strategy from the beginning

      Thx a lot Lars, yesterday I was thinking that the first answer would be from you :-)