java.lang.NumberFormatException Encountered When Switching From SCAN To Non-SCAN Configuration (Doc ID 1538254.1)

Last updated on AUGUST 03, 2016

Applies to:

Oracle Applications Technology Stack - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.

Symptoms

When attempting to switch from SCAN to non-SCAN configuration,
the following error occurs in the database AutoConfig log:

java.lang.NumberFormatException: For input string: "null"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:447)
at java.lang.Integer.parseInt(Integer.java:497)
at oracle.apps.ad.tools.configuration.NetServiceHandler.updateScanParams(NetServiceHandler.java:3066)
at oracle.apps.ad.tools.configuration.NetServiceHandler.main(NetServiceHandler.java:3009)


The issue can be reproduced at will with the following steps:
1. Modify s_scan_name, s_scan_port to "null" in the database context file.
2. Run AutoConfig.


The issue has the following business impact:
Due to this issue, users cannot switch from SCAN to non-SCAN configuration.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms