You can use your valid metalink account. If you dont have than you need to get the oracle CSI number from your team or management team and create the one . Than you can open an SR ( SERVICE REQUEST) in your case issue with oracle . They will respond based on the priority.
Unfortunately, I don't have the metalink account and I think I can't get the one.
Then there is no way to officially report an issue to Oracle. this forum is just a platform Oracle provides for the community.
Also, if your company does not have a support contract (from whence you get a metalink -- aka My Oracle Support -- account) we now know the exact dollar value they place on their data .... zero.
My "...Report an issue to Oracle in Oracle Database." means that there, I feel, a bug or an error in the Oracle Database Software which I needed to report.
8/10 times, when a bug is reported, it's actually the user lacking in the understanding of oracle database's working. You have been asked multiple times that what's this issue that you want to report but you haven't told us. You should share your findings here because there are very well chances that what you may be assuming is a bug , would be proven as a standard functionality.
If you'd care to share it...then we could see if you're right. From there on someone else (not nessecarily SomeoneElse, ofcourse) could report it/file it though, that happens regularly also on http://asktom.oracle.com , for example.
Yes, anybody could do that, but why do you fear that? If you really found a bug (which we still don't know nothing of) then it is very well possible that someone has already reported it to Oracle. Since you do not have access to Metalink/MyOracleSupport, you also do not have access to the bug database. Some contributors on this do have access, I have access too, and could easily check whether you really found a new or already known/old bug.
I really don't see what's the problem or why you should fear this.
You'll need a reproducible testcase, by the way, do you have that?
And what database version are you working with?
I fear, if I open the issue here then anybody can report it to Oracle.
What's to fear about it? It's been a really long thread and despite being asked several times, you are not sharing the so-called "bug" details of yours. Please understand, there is a very high possibility that you are not hitting any bug and even if you are, you may not be the only one and Oracle might be told about it already. But we can only say once we know what you are talking about. So share a reproducible test case here and let's see its really a bug or not.