I would posit that in high functioning engineering organizations ever dev should get experience and in fact target a minumum of 1/3rd of their time be spent on operations work. Ignoring the way your application get's deployed, the environment it has to run in, the systems it needs to integrate with is a great way to build terrible software. Knowing all of that detail makes you a better developer and helps you develop better software. So I don't find it necessarily bad for your career if you end up doing some operations work as a developer. That said you do still want some level of actual development work present so if you don't have any of that then it's a sign of an unhealthy engineering organization.
Now to address the elephant in your comment. Since you mentioned you joined Oracle my advice is to get out as soon as you can. That company is toxic. It's a toxic presence in the database marketplace regardless of how good the database itself is. I've heard it's also a toxic place to work. No idea how much of the workplace stuff is true as opposed to just rumor but it's enough to convince me never to work there.