I've encountered this same problem just the other day. If you're using AspNetProvider and OracleProvider by switching to and from the other, then I'd suggest the following.
I would get an error when I click the Create User link. When I go to Providers to select a provider for each feature, OracleMembershipProvider option was there but AspNetSqlMembershipProvider was not. In the Role Provider section, everything were okay. This shouldn't have happened if didn't experiment on the config files.
I cannot exactly remember what I did but it would be something to do with machine.config and web.config files when I was trying to figure out the solution.
Both membership providers must appear in machine.config file - the AspNetSqlMembershipProvider and the AspNetMembershipProvider.
I tried using <clear /> but it wasn't necesssary here.
The roles providers must also appear - OracleRoleProvider, AspNetSqlRoleProvider, AspNetWindowsTokenRoleProvider in the machine.config file.
In your web.config file, you can specify a default membership provider (e.g. OracleMembershipProvider or AspNetSqlMembershipProvider). Like this one
<membership defaultProvider="OracleMembershipProvider" />
Nothing more, perhaps.
In my understanding, using the <clear/> tag will clear all providers from the defined list before it uses the next-to-be-added provider/s.