Oracle Metalink access for SAP customers

Do you know that Oracle has an Online Support System like OSS which is called Metalink?

Direct Oracle Customers (SAP Customers  who bought Oracle DB License from Oracle, not from SAP) can access this portal. But what about SAP Customers who bought Oracle License from SAP?

I decided to write this tip, as I see that most of Basis Guys don't know that they are able to access Metalink.

Since 2004, SAP customers who uses Oracle as RDBMS can access this portal with the user provided by SAP.

SAP OSS Note 758563: "Oracle Metalink access for SAP customers" gives the valid users and passwords for Metalink Access. You have to supply a valid Service Marketplace user to display this note.

Sorry that I cannot share this info here for legal reasons.

Note is updated, as some customers tries to delete/lock or change password for these users 

SAP Notes : Troubleshoot your SAP ERP problem

SAP Notes give you instructions on how to remove known errors from SAP Systems. They include a description of the symptoms, the cause of the error, and the SAP Release and Support Package level in which the error occurs.

Depending on the type of error, an SAP Note may also include:

· Workarounds

· Descriptions of how to correct repository objects in the ABAP workbench, known as correction instructions

· Links to Support Packages that solve the problem

You can access SAP Notes both from the SAP Service Marketplace and SAPNet - R/3 Frontend.

Caution: The Note Assistant can automatically implement only SAP Notes that have correction instructions.
Read the SAP Note carefully before you use the Note Assistant to implement it. The SAP Note can contain prerequisites, interactions, and references to postprocessing activities (making changes to a table, for example) that you must take into consideration when you implement it.
Technical Details on Correction Instructions Locate the document in its SAP Library structure

Validity

All correction instructions specify the releases and Support Package levels in which you can implement them. These release and Support Package levels are known as the validity range of the correction instructions.

For example, if Support Package 5 corrects and error in Release 4.6C, the validity range of the correction instructions is 4.6C Support Packages 1 -4.

An SAP Note can also determine that correction instructions are not allowed to be implemented if a certain software component (an add-on, for example) exists in the system. This is the case, for example, when a correction changes a program part that is required by another software component in an unaltered form.

If an exception such as this was defined, it is displayed in the header area of the correction instructions, under Invalid for .

The Note Assistant automatically checks the validity and only implements a correction instruction if the system status is within the validity range specified.

Prerequisites

In some cases, you can only implement correction instructions if certain other correction instructions have already been implemented. This is due to related changes made to the same part of the source code, or semantic dependencies.

These dependencies are described in the header area of the correction instructions. These dependencies (prerequisites) mean that you need to implement a sequence of SAP Notes, and not just one SAP Note.