ORA-00201: control file version 18.0.0.0.0 incompatible with ORACLE version 11.2.0.0.0 - NetWeaver

 

Problem:

ORA-00201: control file version 18.0.0.0.0 incompatible with ORACLE version11.2.0.0.0

Solution:

a. Reset COMPATIBLE parameter by SQL> ALTER SYSTEM SET COMPATIBLE = '18.0.0' SCOPE=SPFILE;

b. Then restart database.

        SQL> SHUTDOWN IMMEDIATE

        SQL> STARTUP

Note : SAP Supported Values list all values that are supported for SAP for the given Oracle version.

Oracle Database Release SAP Default Value         SAP Supported Value(s)

11.2.0.1 '11.2.0' (*) '11.2.0' (*)

11.2.0.2 '11.2.0' (*) '11.2.0' (*)

'11.2.0.2' '11.2.0.2'

11.2.0.3 '11.2.0' (*) '11.2.0' (*)

'11.2.0.2' '11.2.0.2'

'11.2.0.3'

11.2.0.4 '11.2.0' (*) '11.2.0' (*)

'11.2.0.2' '11.2.0.2'

'11.2.0.3'

'11.2.0.4'

12.1.0.2 '12.1.0.2.0' '12.1.0.2'

'12.1.0.2.0'

12.2.0.1 '12.2.0.1.0' '12.2.0.1.0'

18.X.Y (18c) '18.0.0' '18.0.0'

19.X.Y (19c) '19.0.0' '19.0.0'

(*) Value COMPATIBLE='11.2.0' is only supported for databases on file system, not for databases in ASM

Fetching Client IP Address in Security Audit logs

 Problem :

You are using a Reverse Proxy or SAP Web Dispatcher to access the Portal and in the Security Audit Logs you want to capture the actual client IP address.

Solution:

Prerequisite - When SAP Web Dispatcher is used as reverse Proxy

1. Configure the proxy to send the IP address of the client in the X-Forwarded-For header.

        When using SAP Web Dispatcher as Reverse Proxy the parameters that needs to added:
wdisp/add_client_protocol_header = true
wdisp/add_xforwardedfor_header = true
wdisp/handle_webdisp_ap_header = true

2. Set the property ClientIpHeaderName to X-Forwarded-For .
Navigate to /nwa -> configuration -> Infrastructure -> Java system properties -> tab 'Services'
HTTP provider -> properties -> ClientIpHeaderName
Modify -> set with value X-Forwarded-For -> Save

3. To enable the use of the X-Forwarded-For header as provider of the terminal client IP address, the  following parameter needs to be set in the ABAP app server:

icm/use_xforwardedfor_header = true

3. Restart to take effect 

Note : For 3rd Party reverse proxy please refer the reverse proxy document, else step 2 and 3 will be the same.

SAP_ABA is in an undefined state that is not safe to be upgraded

 

Error :

Severe error(s) occurred in phase PREP_INIT/VALCHK_INI!
SAP_ABA is in an undefined state that is not safe to be upgraded !!!
EA-APPL is in an undefined state that is not safe to be upgraded !!!
BBPCRM is in an undefined state that is not safe to be upgraded !!!
BI_CONT is in an undefined state that is not safe to be upgraded !!!
PI_BASIS is in an undefined state that is not safe to be upgraded !!!
GW_CORE is in an undefined state that is not safe to be upgraded !!!
CPRXRPM is in an undefined state, that is not safe to be upgraded !!!
MDG_FND is in an undefined state, that is not safe to be upgraded !!!
Reason: Upgrade wasn't completed.

Note : Do not Perform this step when you are in Execution.

Solution:

a. Stop the upgrade.

Change to the upgrade directory:

UNIX: <upgrade directory>/abap/bin

WINDOWS: <upgrade directory>\abap\bin

b. Execute the following command:

UNIX: ./SAPup reset prepare

WINDOWS: .\SAPup.exe reset prepare

c. Rename the current upgrade directory

NOTE: Once you have confirmed that the reset was done properly, you can then delete the directory.

d. Start a new upgrade from scratch.

e. Reset the table buffers in all application servers with the /$TAB command (Enter it in the ABAP system on the GUI window OK-code field).